Claude Skills by sordi-ai

[e.g. "React Best Practices", "Python Type Safety", "AWS Deployment"]

<!-- Use this template when adding a new sub-skill (e.g. skills/go/SKILL.md). Title: feat(skills): add <id> Label: new-skill -->

Git-versioned agent memory — agents that never make the same mistake twice.

<one-sentence trigger condition — when should this skill be loaded? Start with "Apply when ..." for consistency.>

Apply when generating ideas, exploring solution space, or facilitating divergent thinking before committing to an approach.

Apply when closing out a feature branch — pre-merge checklist, rebase, CI verification, cleanup, and post-merge steps.

Apply when writing or refactoring code. Generic rules to prevent the most common review comments — function length, naming, error handling, security, and tooling.

Apply when designing database schemas, writing migrations, or reviewing table structure. Covers naming, keys, indexes, constraints, nullability, and migration safety.

Apply when diagnosing a bug, reproducing a failure, or performing root cause analysis. Covers systematic isolation, binary search, logging strategy, and hypothesis-driven investigation.

Apply when writing or reviewing Dockerfiles, docker compose files, or container build pipelines. Covers layer caching, multi-stage builds, security hardening, and compose conventions.

Apply when documenting project-specific knowledge. Template for ADRs, naming conventions, business rules, and tech-stack quirks.

Apply when creating or reviewing architecture diagrams, Mermaid diagrams, or draw.io files.

Apply when learning from a mistake. Central memory of past errors and derived rules; consult before logging a new error to avoid duplicates.

Apply when building FastAPI endpoints, Pydantic models, or async APIs. Covers routing, dependency injection, error handling, testing, and OpenAPI hygiene.

Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.

Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.

Apply when planning before writing code, defining scope, or producing an implementation plan for a feature or change.

Apply when building LangChain pipelines, LCEL chains, agents, or retrieval-augmented generation systems.

Apply when writing Python code. Type hints, error handling, mutable defaults, async patterns, and packaging conventions.

Apply when writing React components. Hook discipline, state placement, performance, async cleanup, and list keys.

Apply when reviewing code or planning a deployment. Pre-merge checks, migration ordering, rollback strategy, post-deploy verification.

Apply when performing a security review, checking for vulnerabilities, or implementing authentication and authorization logic.

Apply when executing the self-extension workflow. Six steps from a mistake to a merged rule, with CI gates and CODEOWNERS approval.

Apply when writing or reviewing Bash or POSIX shell scripts — automation, CI steps, deploy scripts, or any shell-based tooling.

Apply when editing, generating, or reviewing any SVG diagram. Pixel-perfect Playwright bbox-check is the acceptance test — eyeballing is not sufficient. Run on every SVG before declaring done.

Apply when adding new behavior or fixing a bug. Red-green-refactor cycle, test-first discipline, when TDD doesn't pay.

Apply when writing TypeScript code. Strict types, discriminated unions, async patterns, and runtime safety.