Claude Skills by ATNexusLab

github.com/ATNexusLab

13 skillsA× 130 installs12 views

Api DesignA+++ name = "api-design" description = "Use when designing or reviewing an API contract — REST, GraphQL, RPC, webhooks, events. Resources, methods, status codes, validation, error shape, idempotency, caching, versioning." +++developmentrustsqlVotes: 0GitHub stars: 3
Architecture ReadingA+++ name = "architecture-reading" description = "Use before a non-trivial change in an unfamiliar or large codebase — read it ground → data → backend → frontend → seam, then say where the change belongs and what constrains it." +++developmentrustgoVotes: 0GitHub stars: 3
Database DesignA+++ name = "database-design" description = "Use when modeling data, writing a schema or a migration, or designing queries — keys, constraints, NULL semantics, tenancy, indexes, transactions, safe migrations. Engine-agnostic." +++developmentgoexpressVotes: 0GitHub stars: 3
Frontend ArchitectureAHow the UI is built and how it behaves. **Scope.** Visual craft — palette, type, layout, motion, copy voice — is `frontend-design`. Measuring what it costs is `{{skill:performance-analysis}}`. Mobile-first and the size of a loading state are already rules in the global contract. Framework, router, and data library are the repository's decisions and live in its own `AGENTS.md`; nothing here names one. Written for browser UI: the URL section and bundle cost assume the web. Everything else — sta...developmentrustgoVotes: 0GitHub stars: 3
GrillingADecide everything that can be decided, then show where you might be wrong. **This is not an interview.** The output is a short list of assumptions the user corrects in one pass. A question is what happens *after* a correction leaves a fork you genuinely cannot settle.developmentgogitVotes: 0GitHub stars: 3
Hexagonal ArchitectureAOrganize the code by **business module**, and inside each module apply the hexagon (domain / application / infrastructure). The top level reads as the business; the inside enforces the dependency rule. Compose with `{{skill:architecture-reading}}` — map an existing codebase before restructuring it. **Scope.** This skill names roles, never technologies. The language, the framework, the ORM, the validation library, and the file-extension convention belong to the repository's own `AGENTS.md`.developmentgodatabaseVotes: 0GitHub stars: 3
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Performance AnalysisA+++ name = "performance-analysis" description = "Use when investigating slowness or checking a change for performance impact — set a target, measure at real volume, find where the time goes, fix at the cheapest rung." +++developmentgoapiVotes: 0GitHub stars: 3
Project DocsAEverything under `docs/` is written for people. Big files do not get read, so every doc is a **folder of small files**, one subject each, with a `README.md` as the folder's index. GitHub shows that `README.md` when the folder opens, VS Code shows the tree, and the local docs site turns the same folders into a sidebar with search. Nothing is written twice for any of the three.developmentjavascriptgoVotes: 0GitHub stars: 3
Requirements EngineeringARequirements are not static. They are elicited, analysed, specified, validated, and then **managed**: every change is proposed, analysed for impact, approved, and versioned. A sprint plans against a known version of them.developmentexpressgitVotes: 0GitHub stars: 3
Security AuditARead-only review method: **enumerate the surfaces a change touches, then check each against its required cases.** A surface with a missing case is a finding. **Scope.** This skill names failures, never technologies. The language, the framework, the validation library, and the scanner belong to the repository's own `AGENTS.md`.developmentrustgoVotes: 0GitHub stars: 3
Spec WritingA+++ name = "spec-writing" description = "Use when writing a design document before implementation — a feature spec, an ADR, or acceptance criteria. Carries the templates and the gate that no spec ships with unresolved ambiguity." +++developmentgoapiVotes: 0GitHub stars: 3
Technical WritingAA doc is a claim about the code, and it decays the moment the code moves. Write the fewest docs that answer real questions, put each fact in exactly one place, and prefer the form that cannot go stale. **Scope.** This skill names criteria, never tools. A repo on this workflow takes its docs structure, diagrams, and site from `{{skill:project-docs}}`; any other repo takes them from its own `AGENTS.md`. Project docs live in the **repo** — never only in memory.developmentrustgoVotes: 0GitHub stars: 3
Testing ContractAWhether a test exists and which ones the suite holds is decided in the global contract's **Testing** section. This skill is how to write them. The runner, assertion style, and file layout come from the repo's own `AGENTS.md` and its existing tests — match what is there.developmentsqltestingVotes: 0GitHub stars: 3