Borrowing it
Nothing to install: this file belongs to qingyu321/Little-Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/qingyu321/Little-Claude/main/.claude/commands/trellis/before-frontend-dev.mdgit clone --depth 1 https://github.com/qingyu321/Little-ClaudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/qingyu321/little-claude/before-frontend-dev)<a href="https://agentmods.dev/commands/qingyu321/little-claude/before-frontend-dev"><img src="https://agentmods.dev/badge/commands/qingyu321/little-claude/before-frontend-dev.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00138 |
| Opus 5 | $0.00000 | $0.00069 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
before-frontend-dev 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 6d 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.
This is a copy
100% identical to before-frontend-dev — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Read the frontend development guidelines before starting your development task.
Execute these steps:
- Read
.trellis/spec/frontend/index.mdto understand available guidelines - Based on your task, read the relevant guideline files:
- Component work →
.trellis/spec/frontend/component-guidelines.md - Hook work →
.trellis/spec/frontend/hook-guidelines.md - State management →
.trellis/spec/frontend/state-management.md - Type questions →
.trellis/spec/frontend/type-safety.md
- Component work →
- Understand the coding standards and patterns you need to follow
- Then proceed with your development plan
This step is mandatory before writing any frontend code.
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.
- 6d ago First seen · 14 lines · 0 tokens per session scan A a6225f9d123d
before-frontend-dev is a command published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 138 tokens. A static security scan graded it A with 0 findings. It is 100% identical to before-frontend-dev, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
react-router-client-loader
Do this in a clientLoader and use loaderData to render the component. DO NOT create mock data, new interfaces, or mock data loader functions. Instead, assume loaderData has all of the data you need to render the component.
pn-frontend-redo
Audit-driven frontend remediation on an existing app — baseline audit, slice plan, sequential UI slices with maker-checker gates, preflight, deliver. Use instead of pn-program for same-repo sequential surfaces (Home → fight → chrome). Not for greenfield (pn-design) or parallel vertical slices (pn-program).
pn-audit-a11y
Surgical frontend accessibility audit — WCAG contrast, keyboard navigation, ARIA roles, focus management, and screen-reader compatibility. Standalone or chained by pn-frontend-audit.
pn-audit-layout
Surgical frontend layout audit — spacing tokens, grid consistency, component rhythm, and responsive behavior. Standalone or chained by pn-frontend-audit.
check-cache
Audit caching configuration in $ARGUMENTS for Next.js 15 correctness.