Claude Skills by loiane

github.com/loiane

50 skillsA× 500 installs0 views

Adr AuthoringAAuthor MADR-style Architecture Decision Records under `.specs/<feature-id>/adr/`. Use whenever a non-obvious technical decision is made, a default is overridden, or a waiver is granted.developmentgitapiVotes: 0GitHub stars: 62
Angular DeveloperAGenerates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles), testing, or CLI tooling.developmenttypescriptgoVotes: 0GitHub stars: 62
Angular New AppACreates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.developmenttypescriptgoVotes: 0GitHub stars: 62
Archunit RulesAEncode architecture invariants as ArchUnit rules. Use when defining or reviewing layer boundaries, package dependencies, naming conventions, or cross-module access.developmentjavaspringVotes: 0GitHub stars: 62
Brownfield OnboardingAOnboard an existing Spring codebase into the spec-driven workflow without blocking day one. Establish a `_baseline.json`, ratchet rules, and produce a starter design doc that reflects what the code actually looks like.developmentgojavaVotes: 0GitHub stars: 62
Clarity Over ClevernessAApply clarity-over-cleverness rewrites — prefer code a junior engineer can read at a glance over compact-but-clever code. Use during `/build`'s simplify step and during `/code-simplify` (alias "simplify the code"). Never weakens behavior; suite must remain green.developmentjavaspringVotes: 0GitHub stars: 62
Skills DirectorySkills Directory Pro Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills.See Pro
Ears Spec AuthoringAAuthor acceptance criteria using EARS-lite shapes with stable AC-NNN IDs and explicit Q-NNN open questions. Use when drafting or editing `01-spec.md`, when transforming a tracker ticket into ACs, or when a user asks for a spec / requirements doc.developmentgoVotes: 0GitHub stars: 62
Epic Slicing PlanningAPlan large features by defining high-level Epic architecture and a vertical slice roadmap before detailed implementation tasks. Use during Phase 3 for multi-slice initiatives.developmentgofrontendVotes: 0GitHub stars: 62
Flyway Or Liquibase DetectionAAuto-detect the project's DB migration tool and follow its conventions. Never use both. Use when designing or writing a schema change.developmentsqlspringVotes: 0GitHub stars: 62
Harness Report ParsingAParse harness output (Surefire/Failsafe XML, JaCoCo XML, PIT XML, Checkstyle/SpotBugs XML, OpenAPI diff JSON, dependency-check JSON) into a single structured summary. Use when writing `07-validation-report.md` or when a CI run failed and the agent must explain why.developmentgojavaVotes: 0GitHub stars: 62
Issue Tracker IngestionAPull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into `01-spec.md` `## Source`. Use at the start of `/spec` whenever the user references an external ticket.developmentgoazureVotes: 0GitHub stars: 62
Jacoco Coverage PolicyAJaCoCo configuration and policy enforcement — 90% line+branch floor, 95% target, 95% on new code. Use when wiring JaCoCo into the Maven build or interpreting `jacoco.xml`.developmentgotestingVotes: 0GitHub stars: 62
Junit5 Testcontainers PatternsAJUnit 5 + Spring Boot 4 test slice patterns and Testcontainers integration test patterns with `@ServiceConnection`. Use when writing or reviewing any test, especially when choosing between unit / slice / integration scope.developmentjavasqlVotes: 0GitHub stars: 62
Maven Harness PomAReference Maven POM fragments for the full harness — Spotless, Checkstyle, SpotBugs, Error Prone, JaCoCo, PIT, OpenAPI generator + diff, OWASP dependency check, Surefire/Failsafe. Use when wiring the harness into a new project or upgrading a brownfield POM.developmentgojavaVotes: 0GitHub stars: 62
Openapi Contract FirstAContract-first OpenAPI workflow — author or update the spec, run the diff gate, regenerate types, write the controller. Use when adding or changing an HTTP endpoint.developmentjavaspringVotes: 0GitHub stars: 62
Performance OptimizationASpring Boot 4 / JVM performance work — measure first, then fix. Profiling (async-profiler, JFR, JMH), Micrometer, common Spring antipatterns (N+1, unbounded lists, HikariCP sizing, virtual-thread pinning), caching, GC, and SLO-driven work. Used by `/plan` for risk callouts and by `/review` to flag perf regressions.developmentgojavaVotes: 0GitHub stars: 62
Pit Mutation TuningAConfigure and interpret PIT mutation testing scoped to changed code. Use when adding the mutation gate to a project, when interpreting `mutations.xml`, or when tuning thresholds.developmentgojavaVotes: 0GitHub stars: 62
Requirements TraceabilityABuild and verify the AC ↔ tasks ↔ tests ↔ code symbols ↔ gates traceability matrix in `07a-traceability.md`. Use when validating that no AC is uncovered and no test is orphaned.developmentjavaspringVotes: 0GitHub stars: 62
Shipping And LaunchAPre-deploy hygiene for a Spring Boot 4 feature — verify gates, capture rollback plan, sign off observability, generate release notes, and stage the rollout. Used by `/ship` after `/review` approves the diff. The agent never deploys; it produces the plan a human executes.developmentgosqlVotes: 0GitHub stars: 62
Spring Boot 4 ConventionsASpring Framework 7 / Spring Boot 4 idioms and defaults. Use when writing or reviewing controllers, services, configuration, HTTP clients, async/virtual-thread code, or anything touching Spring's programming model.developmentgojavaVotes: 0GitHub stars: 62
Spring Code Review RubricAPre-commit code review rubric for Spring Boot 4 changes. Used by `spring-code-reviewer` to produce `08-code-review.md` before any commit. Covers traceability, architecture, Spring idioms, error handling, data access, security, test quality, clarity, and migration.developmentjavasqlVotes: 0GitHub stars: 62
Spring Security BaselineAMinimum Spring Security 7 configuration patterns and review baseline. Use when designing or reviewing authentication, authorization, CSRF, CORS, secrets handling, or input validation.developmentrustjavaVotes: 0GitHub stars: 62
Spring Task DecompositionADecompose a Spring Boot 4 design into 1–4 hour TDD-shaped tasks with stable IDs, AC traceability, files-in-scope, and per-task gates. Use when authoring `04-tasks.md`.developmentgojavaVotes: 0GitHub stars: 62
Tdd Red Green RefactorAStrict red/green/refactor/simplify discipline for the `/build <task-id>` command. Use when implementing any task in Phase 4. The agent must NOT write production code without a failing test recorded in `.tdd-state.json`.developmentgojavaVotes: 0GitHub stars: 62
Adr AuthoringAAuthor MADR-style Architecture Decision Records under `.specs/<feature-id>/adr/`. Use whenever a non-obvious technical decision is made, a default is overridden, or a waiver is granted.developmentgitapiVotes: 0GitHub stars: 62
Brownfield OnboardingAOnboard an existing Spring codebase into the spec-driven workflow without blocking day one. Establish a `_baseline.json`, ratchet rules, and produce a starter design doc that reflects what the code actually looks like.developmentgojavaVotes: 0GitHub stars: 62
Clarity Over ClevernessAApply clarity-over-cleverness rewrites — prefer code a junior engineer can read at a glance over compact-but-clever code. Use during `/build`'s simplify step and during `/code-simplify` (alias "simplify the code"). Never weakens behavior; suite must remain green.developmentjavaspringVotes: 0GitHub stars: 62
Ears Spec AuthoringAAuthor acceptance criteria using EARS-lite shapes with stable AC-NNN IDs and explicit Q-NNN open questions. Use when drafting or editing `01-spec.md`, when transforming a tracker ticket into ACs, or when a user asks for a spec / requirements doc.developmentgogitVotes: 0GitHub stars: 62
Epic Slicing PlanningAPlan large features by defining high-level Epic architecture and a vertical slice roadmap before detailed implementation tasks. Use during Phase 3 for multi-slice initiatives.developmentgogitVotes: 0GitHub stars: 62
Issue Tracker IngestionAPull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into `01-spec.md` `## Source`. Use at the start of `/spec` whenever the user references an external ticket.developmentgoazureVotes: 0GitHub stars: 62
Maven Harness PomAReference Maven POM fragments for the full harness — Spotless, Checkstyle, SpotBugs, Error Prone, JaCoCo, PIT, OpenAPI generator + diff, OWASP dependency check, Surefire/Failsafe. Use when wiring the harness into a new project or upgrading a brownfield POM.developmentgojavaVotes: 0GitHub stars: 62
Performance OptimizationASpring Boot 4 / JVM performance work — measure first, then fix. Profiling (async-profiler, JFR, JMH), Micrometer, common Spring antipatterns (N+1, unbounded lists, HikariCP sizing, virtual-thread pinning), caching, GC, and SLO-driven work. Used by `/plan` for risk callouts and by `/review` to flag perf regressions.developmentgojavaVotes: 0GitHub stars: 62
Requirements TraceabilityABuild and verify the AC ↔ tasks ↔ tests ↔ code symbols ↔ gates traceability matrix in `07a-traceability.md`. Use when validating that no AC is uncovered and no test is orphaned.developmentjavaspringVotes: 0GitHub stars: 62
Shipping And LaunchAPre-deploy hygiene for a Spring Boot 4 feature — verify gates, capture rollback plan, sign off observability, generate release notes, and stage the rollout. Used by `/ship` after `/review` approves the diff. The agent never deploys; it produces the plan a human executes.developmentgosqlVotes: 0GitHub stars: 62
Spring Code Review RubricAPre-commit code review rubric for Spring Boot 4 changes. Used by `spring-code-reviewer` to produce `08-code-review.md` before any commit. Covers traceability, architecture, Spring idioms, error handling, data access, security, test quality, clarity, and migration.developmentjavasqlVotes: 0GitHub stars: 62
Spring Task DecompositionADecompose a Spring Boot 4 design into 1–4 hour TDD-shaped tasks with stable IDs, AC traceability, files-in-scope, and per-task gates. Use when authoring `04-tasks.md`.developmentgojavaVotes: 0GitHub stars: 62
Tdd Red Green RefactorAStrict red/green/refactor/simplify discipline for the `/build <task-id>` command. Use when implementing any task in Phase 4. The agent must NOT write production code without a failing test recorded in `.tdd-state.json`.developmentgojavaVotes: 0GitHub stars: 62
Adr AuthoringAAuthor MADR-style Architecture Decision Records under `.specs/<feature-id>/adr/`. Use whenever a non-obvious technical decision is made, a default is overridden, or a waiver is granted.developmentgitapiVotes: 0GitHub stars: 62
Brownfield OnboardingAOnboard an existing Spring codebase into the spec-driven workflow without blocking day one. Establish a `_baseline.json`, ratchet rules, and produce a starter design doc that reflects what the code actually looks like.developmentgojavaVotes: 0GitHub stars: 62
Clarity Over ClevernessAApply clarity-over-cleverness rewrites — prefer code a junior engineer can read at a glance over compact-but-clever code. Use during `/build`'s simplify step and during `/code-simplify` (alias "simplify the code"). Never weakens behavior; suite must remain green.developmentjavaspringVotes: 0GitHub stars: 62
Ears Spec AuthoringAAuthor acceptance criteria using EARS-lite shapes with stable AC-NNN IDs and explicit Q-NNN open questions. Use when drafting or editing `01-spec.md`, when transforming a tracker ticket into ACs, or when a user asks for a spec / requirements doc.developmentgoVotes: 0GitHub stars: 62
Epic Slicing PlanningAPlan large features by defining high-level Epic architecture and a vertical slice roadmap before detailed implementation tasks. Use during Phase 3 for multi-slice initiatives.developmentgofrontendVotes: 0GitHub stars: 62
Issue Tracker IngestionAPull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into `01-spec.md` `## Source`. Use at the start of `/spec` whenever the user references an external ticket.developmentgoazureVotes: 0GitHub stars: 62
Maven Harness PomAReference Maven POM fragments for the full harness — Spotless, Checkstyle, SpotBugs, Error Prone, JaCoCo, PIT, OpenAPI generator + diff, OWASP dependency check, Surefire/Failsafe. Use when wiring the harness into a new project or upgrading a brownfield POM.developmentgojavaVotes: 0GitHub stars: 62
Performance OptimizationASpring Boot 4 / JVM performance work — measure first, then fix. Profiling (async-profiler, JFR, JMH), Micrometer, common Spring antipatterns (N+1, unbounded lists, HikariCP sizing, virtual-thread pinning), caching, GC, and SLO-driven work. Used by `/plan` for risk callouts and by `/review` to flag perf regressions.developmentgojavaVotes: 0GitHub stars: 62
Requirements TraceabilityABuild and verify the AC ↔ tasks ↔ tests ↔ code symbols ↔ gates traceability matrix in `07a-traceability.md`. Use when validating that no AC is uncovered and no test is orphaned.developmentjavaspringVotes: 0GitHub stars: 62
Shipping And LaunchAPre-deploy hygiene for a Spring Boot 4 feature — verify gates, capture rollback plan, sign off observability, generate release notes, and stage the rollout. Used by `/ship` after `/review` approves the diff. The agent never deploys; it produces the plan a human executes.developmentgosqlVotes: 0GitHub stars: 62
Spring Code Review RubricAPre-commit code review rubric for Spring Boot 4 changes. Used by `spring-code-reviewer` to produce `08-code-review.md` before any commit. Covers traceability, architecture, Spring idioms, error handling, data access, security, test quality, clarity, and migration.developmentjavasqlVotes: 0GitHub stars: 62
Spring Task DecompositionADecompose a Spring Boot 4 design into 1–4 hour TDD-shaped tasks with stable IDs, AC traceability, files-in-scope, and per-task gates. Use when authoring `04-tasks.md`.developmentgojavaVotes: 0GitHub stars: 62
Tdd Red Green RefactorAStrict red/green/refactor/simplify discipline for the `/build <task-id>` command. Use when implementing any task in Phase 4. The agent must NOT write production code without a failing test recorded in `.tdd-state.json`.developmentgojavaVotes: 0GitHub stars: 62