solid-astro

An Astro project code-organisation guide based on SOLID design principles, which encourage small, focused, reusable parts.

In plain words
What is it for?
Use it when structuring Astro components, layouts, services, interfaces, and utilities, and when checking that new code follows the project's patterns.
Why use it?
It sets boundaries for file sizes, types, documentation, and shared code so the project is easier to change and maintain.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/fusengine/agents/solid-astro
Any agent
npx skills add fusengine/agents --skill solid-astro
Clone the repo
git clone --depth 1 https://github.com/fusengine/agents

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 972 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00972
Opus 5 $0.00017 $0.00486
Sonnet 5 $0.00007 $0.00194
Haiku 4.5 $0.00003 $0.00097

Measured 2d ago against content hash 7bba689f38a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

solid-astro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/astro-expert/skills/solid-astro/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Provides ready-to-copy templates for components, layouts, services, and interfaces that already follow these rules. This is a cross-cutting code-quality skill, not a feature skill — it doesn't teach Astro APIs themselves (see astro-7, astro-content, astro-i18n, astro-styling for that), only how to structure the code that uses them.

SOLID Astro — Modular Architecture

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

  1. fuse-ai-pilot:explore-codebase - Analyze project structure, naming, and existing patterns
  2. fuse-ai-pilot:research-expert - Verify Astro 7 architecture best practices via Context7/Exa
  3. 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:

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

DRY Enforcement (MANDATORY)

Before writing ANY new code:

  1. Grep for similar logic — function names, class patterns, component names
  2. Check src/lib/ for existing utilities
  3. Check src/components/ for existing UI components
  4. If logic appears in 2+ places → extract to src/lib/
  5. 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/

Read the full file on GitHub · 98 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 98 lines · 35 tokens per session scan A 7bba689f38a5

Subscribe to this mod's changes

solid-astro is a skill published in the GitHub repository fusengine/agents (25 stars, last pushed 29d ago), licensed MIT. It adds 35 tokens to every session and 972 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.