Skill

solid-astro

Use when applying SOLID principles and clean architecture to Astro projects. Enforces files < 100 lines, src/interfaces/ for types, JSDoc on all exports, modular directory structure, and DRY enforcement.

From fuse-astro

Install

Run in your terminal

npx claudepluginhub fusengine/agents --plugin fuse-astro

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/architecture.md

references/dry-enforcement.md

references/file-limits.md

references/interfaces.md

references/jsdoc.md

references/solid-principles.md

references/templates/component.md

references/templates/interface.md

references/templates/layout.md

references/templates/service.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

SOLID Astro — Modular Architecture

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

fuse-ai-pilot:explore-codebase - Analyze project structure, naming, and existing patterns
fuse-ai-pilot:research-expert - Verify Astro 6 architecture best practices via Context7/Exa
mcp__context7__query-docs - Check Astro component API and TypeScript integration

After implementation, run fuse-ai-pilot:sniper for validation.

Codebase Analysis (MANDATORY)

Before ANY implementation:

Explore src/ directory to understand existing architecture
Read existing similar files to follow established naming and patterns
Grep for similar function/component names before creating new ones
Identify where interfaces, utilities, and shared logic live

DRY Enforcement (MANDATORY)

Before writing ANY new code:

Grep for similar logic — function names, class patterns, component names
Check src/lib/ for existing utilities
Check src/components/ for existing UI components
If logic appears in 2+ places → extract to src/lib/
If types appear in 2+ files → move to src/interfaces/

Absolute Rules

Files < 100 lines — split at 90
All types in src/interfaces/ — never in component files
JSDoc mandatory on all exported functions
No business logic in src/pages/

See references/architecture.md, references/file-limits.md, references/solid-principles.md.

Reference Guide

Concepts

Topic	Reference	When to Consult
SOLID principles	solid-principles.md	Architecture decisions
File limits	file-limits.md	When and how to split files
Interfaces	interfaces.md	TypeScript type organization
Architecture	architecture.md	Directory structure
DRY enforcement	dry-enforcement.md	Avoiding duplication
JSDoc	jsdoc.md	Documentation standards

Templates

Template	When to Use
component.md	Astro component with props + JSDoc
layout.md	Layout component with slots
service.md	Data fetching service function
interface.md	TypeScript interface file

Forbidden

Files > 100 lines (split at 90)
TypeScript interfaces in component .astro files
Business logic in src/pages/ files
Direct CMS/API calls in components (use src/lib/ services)
Copy-pasting logic instead of extracting shared function
Missing JSDoc on exported functions, components, and types
any TypeScript type