All authors
Claude Skills by trungdo9
github.com/trungdo9112 skills3 installs101 views
- SecurityComplete security suite — expert mindset + active code scanner. Covers OWASP 2025, supply chain, L1-L4 data flow analysis, 21 vulnerability rules with a cost-tiered default pass, TINY/SMALL/LARGE scan modes, bilingual output (vi/en). Use when scanning code for security vulnerabilities, doing security audits, or applying security mindset. Triggers on "scan security", "kiểm tra bảo mật", "security audit", "review security".Votes: 0GitHub stars: 3
- Show OffCreate visually impressive HTML showcases using Tailwind CSS for product demos, landing pages, and social mediaVotes: 0GitHub stars: 3
- TddRed-green test-driven discipline — NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Use for bug fixes (default), regression-prone changes, or when asked to "write tests first" / "TDD this". Covers red → verify-red → green → verify-green → refactor, the baseline rule (baseline-first, never git stash), the rationalization table, and red flags. Discipline only — test infra and browser toolkits live in test-automation, case derivation in scenario.Votes: 0GitHub stars: 3
- TeamOrchestrate parallel multi-session collaboration with independent Claude Code teammates. CK-native (v2.1.0) engine that spawns independent Claude Code sessions as teammates — each with own context window, task ownership, and persistent cross-session memory. Use when 3+ independent workstreams must run in parallel, workers need to discuss findings, competing hypotheses need evaluation, or multi-layer work (API + UI + DB) benefits from per-layer ownership.Votes: 0GitHub stars: 3
- To TicketsBreak a plan, spec, or the current conversation into vertical tracer-bullet tickets, each declaring the tickets that block it — written as one file per ticket under plans/<plan-dir>/tickets/, or published as issue-tracker sub-tasks under a parent issue on explicit opt-in. Use when a plan needs slicing into independently shippable units, when work is handed to parallel agents or devs, or when a wide refactor needs an expand–contract sequence. Triggers on "break this into tickets", "slice the p...Votes: 0GitHub stars: 3
- Verify PlanFalsify a plan's factual claims before implementing against them. Use before executing any plan written in another session (/ck:cook --from-plan), via /ck:plan verify <path>, or whenever a plan asserts existing-behaviour facts (a root cause, "X currently does Y", affected row counts, "already done"). Produces a claim → verdict → evidence table; no code until it is approved.Votes: 0GitHub stars: 3
- DeliverRender the six downstream delivery documents — Scope Statement, UAT Report, Acceptance Record, Release Notes, Go-Live Checklist, Handover Brief — deterministically from the BA entity tree. Use via /ba:deliver when a project needs a signed-off delivery artifact, or to re-derive a derived document after the entity tree changed.Votes: 0GitHub stars: 3
- DiagrammingDraw BA diagrams in mermaid — sequence, flow, state, erd — derived from the entity spine first, free text second, and ship every one compiled or labelled [UNRENDERED], never a third state. Use when a PRD/SRS needs a picture of who-calls-whom, a decision flow, an entity's lifecycle, or the data model, or before /ba:spec compose embeds one.Votes: 0GitHub stars: 3
- PrdWrite the product-definition entity pair — PRD-001 plus one EPIC per user-visible capability — from plans/ba-context.md, then order the existing EPIC set into a Now/Next/Later roadmap without inventing new entities. Use when a project has a context hub but no PRD yet, before /ba:spec derives FRs from EPICs, or to re-sequence an existing roadmap.Votes: 0GitHub stars: 3
- SpecWrite the six spec entities — FR, NFR, UC, US, AC, TC — each strictly derived from the kind above it in the chain, then compose them into the two signed deliverables PRD-001.md and SRS-001.md. Use when a project has EPICs but no FRs yet, before writing a UC/US/AC/TC, or before /ck:tickets needs a signed SRS.Votes: 0GitHub stars: 3
- TraceabilityAssign a stable id to every business-analysis requirement and record its parent graph as one markdown file per entity, so gap/doc-drift/CR-impact/dashboard/knowledge-graph views can all be built off one index instead of five bespoke features. Use when authoring or validating a PRD/SRS/EPIC/FR/NFR/UC/US/AC/TC entity, before signing off a deliverable, or before `/ba:qc gap`.Votes: 0GitHub stars: 3
- ContextFoundation BA skill. Create or update the BA context hub (plans/ba-context.md) — scope, actors, system boundary, sources, NFRs, glossary, sign-off, tracker. Read by /ba:plan; every other /ba: command hard-fails without it.Votes: 0GitHub stars: 3