xbklairith/kisune

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Collaborative refinement of rough ideas into clear requirements/designs through systematic questioning. Use when requirements are vague or exploring architectural options.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Use when about to claim work is complete, fixed, passing, or ready to commit/PR — requires running verification commands and reading fresh output before any success claim. Evidence before assertions, always.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Rewrite engineer-to-engineer content for leadership audiences — VPs, directors, PMs, release managers. Shapes for the channel: JIRA comment, Slack post, standup note, email, or meeting talking-points. Use after post-mortem or any technical update that needs to flow up the org.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Smart git operations — commit messages, branch management, PR creation with summaries. Use for any git workflow.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Use after a debug session lands a validated fix, before closing the bug.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

25-point code quality checklist covering structure, errors, security, performance, and testing. Use before commits or when reviewing code.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Outsider-perspective deep review of a plan, PR, design doc, or code change — questions intent first (should this exist?), then traces the actual code path end-to-end to verify the change does what it claims. Use for serious PR reviews, design audits, or second opinions. Lighter pre-commit checks use review instead.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

OWASP Top 10 vulnerability detection. Use PROACTIVELY for code handling user input, auth, APIs, payments, or sensitive data.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Create and edit Claude Code skills with TDD methodology. Use when creating or editing skills. Test with subagents before deployment, iterate until bulletproof.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Use when facing 2+ independent problems (different test files, unrelated bugs, separate subsystems) that can be investigated in parallel without shared state — covers the dispatch decision, the actual Claude Code parallelism mechanism, prompt construction, and integration after agents return.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Execute spec-driven implementation — auto-detects Quick (plan.md) or Full (tasks.md) mode and runs step-by-step with verification. Use when implementing a planned feature or running TDD tasks.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Plan new features using spec-driven workflow — auto-picks Quick (single plan.md) or Full (3-file EARS spec) mode. Use when creating features, writing requirements, or designing architecture.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Review feature spec files with 3 focused agents — spec quality (business+correctness+ambiguity), completeness (missing scenarios+safety+testability), and buildability (compatibility+blockers+traceability). Sequential by default.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Systematic debugging framework — opens every session by reciting the 4-mantra block (reproduce, trace the fail path, falsify the hypothesis, cross-reference breadcrumbs), then applies multi-layer investigation. Use when diagnosing bugs, flaky tests, unknown failures, or cross-component issues.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Strict RED-GREEN-REFACTOR enforcement with no exceptions. Use when implementing features or fixing bugs. No production code without a failing test first.

xbklairith/kisune

Skill Claude CodeCodex

Part of dev-workflow

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions.

xbklairith/kisune

Skill Claude CodeCodex

Part of trading

Technical analysis with indicators (RSI, MACD, MA), support/resistance, multi-timeframe trends, and sentiment. Use when analyzing markets or interpreting charts.

xbklairith/kisune

Skill Claude CodeCodex

Part of trading

Chart pattern identification — head and shoulders, double tops, triangles, flags. Documents pattern library with entry/exit criteria.

xbklairith/kisune

Skill Claude CodeCodex

Part of trading

Systematic trading strategy research — edge hypothesis, statistical validation, and strategy documentation (entry, exit, risk management).

xbklairith/kisune

Skill Claude CodeCodex

Part of trading

Convert strategy docs to Python (pandas, framework-agnostic) and TradingView Pine Script v5. Use when translating strategies to code for backtesting.

xbklairith/kisune

Skill Claude CodeCodex

Shared vocabulary for designing deep modules — module, interface, depth, seam, adapter. Use when designing or improving a module's interface, deciding where a seam goes, hunting for deepening opportunities, or making code more testable.

xbklairith/kisune

Skill Claude CodeCodex

Build and sharpen a project's domain model — challenge terms, resolve them into a glossary, and record hard-to-reverse decisions as ADRs. Use when codebase terminology is fuzzy or contested, when writing or editing a glossary, or when recording an architectural decision.

xbklairith/kisune

Skill Claude CodeCodex

Grilling that leaves a paper trail — runs the grilling interview while capturing resolved terminology and hard-to-reverse decisions into docx/ as they settle.

xbklairith/kisune

Skill Claude CodeCodex

Relentless round-based interview that stress-tests a plan before building. Maps the plan as a design tree and works it in rounds, asking every unblocked question at once with a recommended answer for each, until nothing is left silently assumed.