1 files
ALWAYS activate before implementing ANY feature, plan, or fix.
source snapshot Aug 22, 2026
Topic / 06 skills
Implementation
Source-linked DevKit workflows classified under implementation.
| Skill / purpose | Topics | Snapshot | Files |
|---|---|---|---|
| hi-craft ALWAYS activate before implementing ANY feature, plan, or fix. baka3k/dev-kit Mainverified | Aug 22, 2026 | 1 | |
| hi-fix ALWAYS activate before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem. baka3k/dev-kit Mainverified | Aug 15, 2026 | 5 | |
| hi-api-contract-discovery Produce draft-only evidence-backed HTTP and asynchronous API contracts, including OpenAPI or AsyncAPI drafts, endpoints, messages, schemas, authentication, authorization, errors, consumers, and providers. Do not deploy APIs, modify implementations, or publish inferred contracts as authoritative. baka3k/dev-kit Mainverified | Aug 15, 2026 | 4 | |
| hi-brainstorm Convene an adaptive panel of independent experts to generate competing solutions, challenge assumptions, debate tradeoffs, and select an evidence-backed option with weighted scoring before implementation. Use for ambiguous, consequential, or multi-path decisions; skip trivial work with one obvious reversible solution. baka3k/dev-kit Mainverified | Aug 22, 2026 | 2 | |
| hi-command-spec-discovery Produce draft-only special command or protocol wire-format specification from implementation code, including APDU/TLV fields, CLA/INS/P1/P2/Lc/Le framing, opcodes, status words, and command-specific models. Do not use for business scenarios, API contracts, or standalone behavior modeling. baka3k/dev-kit Mainverified | Aug 22, 2026 | 5 | |
| hi-repository-search Gather traceable evidence from repository code and project documents. Use for codebase exploration, architecture, feature tracing, dependency or impact analysis, and questions that require verified source context. baka3k/dev-kit Mainverified | Aug 22, 2026 | 3 |
5 files
ALWAYS activate before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem.
source snapshot Aug 15, 2026
4 files
Produce draft-only evidence-backed HTTP and asynchronous API contracts, including OpenAPI or AsyncAPI drafts, endpoints, messages, schemas, authentication, authorization, errors, consumers, and providers. Do not deploy APIs, modify implementations, or publish inferred contracts as authoritative.
source snapshot Aug 15, 2026
2 files
Convene an adaptive panel of independent experts to generate competing solutions, challenge assumptions, debate tradeoffs, and select an evidence-backed option with weighted scoring before implementation. Use for ambiguous, consequential, or multi-path decisions; skip trivial work with one obvious reversible solution.
source snapshot Aug 22, 2026
5 files
Produce draft-only special command or protocol wire-format specification from implementation code, including APDU/TLV fields, CLA/INS/P1/P2/Lc/Le framing, opcodes, status words, and command-specific models. Do not use for business scenarios, API contracts, or standalone behavior modeling.
source snapshot Aug 22, 2026
3 files
Gather traceable evidence from repository code and project documents. Use for codebase exploration, architecture, feature tracing, dependency or impact analysis, and questions that require verified source context.
source snapshot Aug 22, 2026