.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/loiane/specs-driven-development-spring-angular
home/subagents/loiane/specs-driven-development-spring-angular
loiane avatar

loiane/specs-driven-development-spring-angular

12 subagents

View on GitHub
Subagent
angular-architectPhase 3 — design the Angular feature, decompose into TDD-shaped frontend tasks, write ADRs. Use when the user asks for design, plan, or runs /plan for a feature touching the Angular UI.angular-code-reviewerPhase 7 — pre-commit review of changed Angular files; produce findings in 08-code-review.md covering correctness, accessibility, performance, security, test quality, and clarity. Use when running…angular-implementerPhase 4 (green/refactor/simplify) — minimum Angular production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.angular-test-engineerPhase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build <task-id> for frontend tasks.angular-validatorPhase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular…spec-authorPhase 1+2 — author and review the EARS-lite spec for a Spring Boot 4 feature. Use proactively when the user asks for a spec, requirements, or runs /spec or /spec-review.spring-architectPhase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.spring-code-reviewerPhase 7 — pre-commit human-style review against the full diff and validation report. Produce 08-code-review.md and final verdict; block commit on unwaived blockers.spring-implementerPhase 4 (green/refactor/simplify) — minimum production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.spring-onboardingBootstrap an existing Spring codebase into the spec-driven workflow. Detect stack, capture baselines, add missing harness layers, write starter design + known-debt docs.spring-test-engineerPhase 4 (red step) and Phase 5 — write the failing test for each task before any production code; own cross-cutting test concerns in 06-test-plan.md.spring-validatorPhase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.