Your architecture diagrams lie. Your team ships features but users don't adopt them. Your "microservices" are just a distributed monolith.
These skills give Claude the vocabulary and frameworks to help you fix that β diagnosing delivery with DORA, modeling domains with DDD, mapping architecture honestly with C4, and tracking whether your releases actually spread via Rogers Diffusion.
Works with Claude Code, Gemini CLI, Cursor, and Qwen.
- Agent as Domain Expert: Each agent operates as a specialist β Strategy Consultant, Product Manager, Domain Architect, Software Engineer. They follow established frameworks and cite sources.
- User Sovereignty: The agent proposes. The user decides. The agent executes. Agents never make irreversible decisions without consent.
- Design-to-Code Sync: Architectural diagrams (C4) must reflect the reality of the codebase.
- Domain-Driven Excellence: The "heart of software" is the domain model (DDD).
- Ship != Release: Decouple technical deployment from business value delivery.
- Evidence-Based Discovery: Use Product Market Research and Jobs-To-Be-Done (JTBD) to build what matters.
- Measure Delivery: DORA metrics (Deployment Frequency, Lead Time, CFR, MTTR) ensure the team can actually ship.
Designed for Product Owners, Architects, and Developers to work in total alignment.
π Master Framework | Second Brain Guide | Antigravity Workflow | Art of War Strategy Guide | Business Leadership Guide | C4 & DDD Mapping Guide
| Phase | Skill | Outcome |
|---|---|---|
| Strategy Audit | art-of-war-software-engineering | The Five Factors (NgΕ© Sα»±) Assessment |
| Strategy | business-product-leadership | Product Market Research, JTBD, Diffusion of Innovations |
| Discovery | ddd-core | Event Storming β Bounded Contexts |
| Release Tracking | diffusion-release-tracking | Rogers Bell Curve β Go/No-Go per gate |
| Delivery | business-product-leadership | Ship vs. Release, MVP Playbook |
| Performance | dora-core | Deployment Frequency, Lead Time, CFR, MTTR tiers |
| Level | Skill | Focus |
|---|---|---|
| L1 | c4-level1-context | System Scope & User Journeys (Tech-free) |
| L2 | c4-level2-container | Infrastructure & Deployment (Docker/K8s) |
| L3 | c4-level3-component | Internal Code Structure & Folder Mapping |
| Code | clean-architecture | Dependency Rule, Ports & Adapters, Package by Component |
| Tactical | ddd-tactical | Rich Domain Models & Scoring Rubric (0-10) |
| Advanced | ddd-patterns | CQRS, Event Sourcing, Outbox, ACL |
| Skill | Description |
|---|---|
| art-of-war-software-engineering | Apply Sun Tzu's "Art of War" principles to software strategy, engineering leadership, and tactical execution. |
| why-strategic-rationale | Strategic rationale via Value Proposition Canvas + Amazon Working Backwards PR/FAQ. |
| business-product-leadership | Product Market Research, JTBD, Diffusion of Innovations, MVP Planning, Ship != Release, NotebookLM Grounded Reasoning. |
| diffusion-release-tracking | Rogers Bell Curve tracking with 4 phase-gated Go/No-Go release decisions (Innovator β Early Adopter β Chasm β Majority). |
| dora-core | DORA metrics (DF, LT, CFR, MTTR) with Elite/High/Medium/Low tiers and capability gap analysis. |
| collaborative-engineering-agent | Unified SDLC: Agile PM, GitOps/SecOps, Dialectical Review Engine, DORA-aligned practices. |
| Skill | Description |
|---|---|
| ddd-core | Strategic DDD: Event Storming, Subdomains, Bounded Contexts. |
| ddd-tactical | Tactical DDD: Aggregates, Value Objects, Scoring Rubric. |
| ddd-patterns | Advanced: CQRS, Event Sourcing, Outbox, ACL. |
| c4-model | Navigation hub, anti-patterns, stakeholder mapping. |
| c4-level1-context | System Context & User Journeys (PM-friendly). |
| c4-level2-container | Infrastructure & Deployment Mapping. |
| c4-level3-component | Internal Code Structure & Folder Mapping. |
| c4-level4-code | Implementation details (UML & ER Diagrams). |
| clean-architecture | Dependency Rule, Layers, Ports & Adapters, Package by Component. |
| Skill | Description |
|---|---|
| kinhluan-router | Central dispatcher β routes requests to correct skill based on workflow stage and artifact detection. |
| agent-expertise-protocol | Defines agent behavior: expertise domains, user sovereignty, Master Framework compliance, escalation rules. |
| Category | Skills |
|---|---|
| Languages | Python, JS/TS, Go |
| Infrastructure | Docker, Kubernetes |
| Security | Security Analysis |
| ML Systems | Scheduling Algorithms, Federated RL |
End-to-end workflow from literature survey to defense. Each skill connects to the next.
| Stage | Skill | Purpose |
|---|---|---|
| 1. Survey | sota-survey | Search, triage, synthesize literature β gap matrix |
| 2. Formulate | research-question | RQ, hypothesis, contribution statement |
| 3. Propose | phd-proposal | Write proposal per IEEE/ACM CS standards |
| 4. Design | research-design | Experiment protocol, baselines, metrics, ablation |
| 5. Execute | experiment-tracking | Log, compare, debug, reproduce experiments |
| 6. Write | paper-writing | Draft paper/thesis section-by-section + LaTeX |
| 7. Critique | internal-critique | Self-review, simulate tough reviewer |
| 8. Publish | publication-strategy | Venue selection, rebuttal, revision cycles |
| 9. Defend | defense-prep | Slides, Q&A simulation, day-of checklist |
| β Track | milestone-tracker | PhD timeline, deadlines, committee meetings |
Also see: product-analytics for metrics and experimentation, product-ux-research for user research methods.
/plugin marketplace add kinhluan/skills
/plugin install kinhluan-skills
/reload-plugins
Skills available as kinhluan-skills:<skill-name> (e.g. kinhluan-skills:dora-core).
npx skills add kinhluan/skillsmake validate: Ensure all skills follow the skills.sh standard.make package: Build.skilldistribution files indist/.
- LuΓ’n B. - luanbhk@gmail.com
MIT License - see LICENSE for details.