guide: Command for Claude Code

.github/workflows/generate-ai-rules/commands/scaffold-frontend-project.md

scaffold-frontend-project is a command for Claude Code from rios0rios0/guide. It costs 0 tokens per session (1,094 once invoked), scanned A, original, MIT.

A command that creates a new frontend project with five separated layers: business concepts, services, technology details, user interface, and application setup.

In plain words
What is it for?
Use it to scaffold TypeScript frontend projects with folders and starter files for entities, API services, infrastructure, views, hooks, providers, and dependency setup.
Why use it?
It gives a new project a consistent structure and keeps technology-specific code from spreading into the core business logic.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

This is rios0rios0/guide's own configuration. It tells Claude Code how to work on guide itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything guide configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { User } from '../entities/user';.

Part of the engineering-standards plugin — 5 skills, 8 commands, 7 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to rios0rios0/guide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rios0rios0/guide/main/.github/workflows/generate-ai-rules/commands/scaffold-frontend-project.md
Clone the repo
git clone --depth 1 https://github.com/rios0rios0/guide

Made for: Claude Code.

Or install engineering-standards, the plugin that ships this one along with the rest of its 5 skills, 8 commands, 7 agents.

Wrote 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.

agentmods badge for scaffold-frontend-project

README.md
[![agentmods](https://agentmods.dev/badge/commands/rios0rios0/guide/scaffold-frontend-project.svg)](https://agentmods.dev/commands/rios0rios0/guide/scaffold-frontend-project)
Your own site
<a href="https://agentmods.dev/commands/rios0rios0/guide/scaffold-frontend-project"><img src="https://agentmods.dev/badge/commands/rios0rios0/guide/scaffold-frontend-project.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,094 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01094
Opus 5 $0.00000 $0.00547
Sonnet 5 $0.00000 $0.00219
Haiku 4.5 $0.00000 $0.00109

Measured 7d ago against content hash 37badb3aeeff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

scaffold-frontend-project 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 7d 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.

.github/workflows/generate-ai-rules/commands/scaffold-frontend-project.md · 169 lines

How it starts

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

Scaffold a new frontend project following the 5-layer Clean Architecture (Domain, Service, Infrastructure, Presentation, Main).

For architecture details, refer to the Frontend Design section of the Architecture rule. For TypeScript standards, refer to the JavaScript rule. For testing patterns, refer to the Testing rule. For Makefile setup, refer to the CI/CD rule.

5-Layer Architecture

Domain            (most abstract -- entities and contracts)
  ^
Service           (API and external service communication)
  ^
Infrastructure    (technology-specific implementations)
  ^
Presentation      (views and UI components)
  ^
Main              (DI wiring, providers -- "dirty" layer)

Dependencies ALWAYS point towards Domain. Main is the only layer that knows about all others.

Directory Structure

src/
├── domain/
│   ├── entities/
│   │   └── user.ts
│   └── contracts/
│       └── user_repository.ts
├── service/
│   └── user_service.ts
├── infrastructure/
│   └── http_user_repository.ts
├── presentation/
│   ├── components/
│   │   └── user_list.tsx
│   ├── pages/
│   │   └── users_page.tsx
│   └── hooks/
│       └── use_users.ts
├── main/
│   ├── providers/
│   │   └── user_provider.tsx
│   ├── di/
│   │   └── container.ts
│   └── app.tsx
└── index.tsx

Step-by-Step

1. Create the Domain layer -- entities and repository contracts

// src/domain/entities/user.ts
export interface User {
  id: string;
  name: string;
  email: string;
}

// src/domain/contracts/user_repository.ts
import { User } from '../entities/user';

export interface UserRepository {
  findAll(): Promise<User[]>;
  findById(id: string): Promise<User | null>;
}

2. Create the Service layer

// src/service/user_service.ts
import { User } from '../domain/entities/user';
import { UserRepository } from '../domain/contracts/user_repository';

export class UserService {
  constructor(private readonly repository: UserRepository) {}

  async listUsers(): Promise<User[]> {
    return this.repository.findAll();
  }
}

Read the full file on GitHub · 169 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. 7d ago First seen · 169 lines · 0 tokens per session scan A 37badb3aeeff

Subscribe to this mod's changes

scaffold-frontend-project is a command published in the GitHub repository rios0rios0/guide (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,094 tokens. 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-31.

Related

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…

yonatangross/orchestkit · 74 tokens

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.

iloveitaly/llm-ide-rules · 0 tokens

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).

perniemann/pnCore · 69 tokens

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.

perniemann/pnCore · 43 tokens

pn-audit-layout

Surgical frontend layout audit — spacing tokens, grid consistency, component rhythm, and responsive behavior. Standalone or chained by pn-frontend-audit.

perniemann/pnCore · 35 tokens

ui-test

A UI review command that changes an interface to match a design and then checks the result in a real browser.

xcodethink/open-claude-code-skills · 32 tokens