claude

casf

Turns a rough idea into a production-grade project spec and a working app, with 14 specialist subagents and a 25-chapter engineering constitution.

3 on GitHubby Andy León Verav1.0.0MITupdated 7 days ago
/

Plugin casf from marketplace casf in ZoodiacR/CASF. Commands read from the repo's manifest — 7 days ago.

What it installs

Skills (1)

  • casf-framework

    Operating manual for the CASF framework. Use when the user wants to turn a rough idea into a project spec, scaffold or build a full application, or run the agent delegation and quality-gate loop. Do not use for one-off coding questions.

Subagents (14)

  • architecture-reviewer

    Hunts mismatches between a design's intent and the delivered code by testing the architect's hypotheses against the real source. Use when a slice of implementation is called complete, when an app is about to be treated as production-ready, or when a refactor needs an evidence-based verdict.

  • backend-architect

    Designs REST APIs with OpenAPI contracts, service-layer patterns, async jobs, rate limiting and request tracing. Use when a feature needs an API design, when service boundaries or background processing change, or when backend performance and refactoring decisions arise.

  • chief-engineer

    Owns the system architecture, authors and approves ADRs, and resolves conflicts between specialist agents. Use for architectural design of new features, sign-off on cross-cutting technical changes, technical debt prioritization, or when specialists disagree on an approach.

  • code-reviewer

    Runs the final review before merge, verifying the Definition of Done and quality gates and blocking changesets that violate standards. Use when a pull request or slice of work needs verification, or when quality-gate failures, coverage gaps or documentation gaps surface.

  • context-manager

    Guarantees session continuity by owning and incrementally updating the progress checkpoint file. Use at session start, after each completed task, before destructive or long-running actions, and whenever context-window exhaustion or a resume or status request occurs.

  • cost-accountant

    Tracks token usage and computes LLM and API cost in a running ledger so the user knows what a session or project costs. Use on session boot, after each agent turn or API call, and when a budget threshold is crossed or a status or ship report needs a cost summary.

  • database-architect

    Designs normalized schemas, versioned migrations, index strategy and transactional integrity. Use for new data models, schema migrations, query performance or N+1 problems, data-integrity issues, and backup, recovery or sharding decisions.

  • devops-engineer

    Owns CI/CD pipelines, infrastructure as code, environments, secrets, monitoring and rollback strategy. Use when setting up builds or deployments, changing infrastructure, designing observability or secret management, or resolving environment parity issues.

  • documentation-writer

    Keeps README, ADRs, API docs, changelogs and runbooks synchronized with the code. Use when a feature or release needs documentation updates, an API or architectural decision changes, or a merge requires docs review and synchronization.

  • frontend-architect

    Owns UI component architecture, state management, responsive design, accessibility and Core Web Vitals. Use for new pages or features, component library work, state architecture decisions, accessibility audits, and frontend performance or XSS and CSP concerns.

  • project-orchestrator

    Top-level coordinator that turns user intent into plans, delegates to specialist agents and enforces the Definition of Done. Use when a slash command is invoked, a new feature or requirement arrives, status is requested, or a quality-gate failure or incident needs coordination.

  • qa-engineer

    Owns test strategy, unit, integration and e2e suites, coverage gates and regression testing. Use when a feature needs a test plan, coverage gates fail, flaky tests appear, or e2e journeys, test environments and test data need design.

  • security-officer

    Handles threat modeling, authentication and authorization, secrets, dependency audits and OWASP compliance. Use when a new feature needs a security review, auth design is required, vulnerabilities or incidents surface, or secrets and compliance need assessment.

  • spec-quality-reviewer

    Scores generated project specs against the quality rubric before any build, flagging thin specs and red-line failures. Use when a spec is generated or edited in CASF Studio, or when the generator prompt changes and needs regression checking.

View source on GitHub

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

Maintain casf?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted