DevKit

A token-efficient agent skills kit for software engineering workflows. 16 composable skills, designed for Claude Code / Cursor / Continue / Copilot...etc

Advanced Capabilities

Integrated with Cortex Harness, the Dev Kit delivers an end-to-end Software Development Life Cycle (SDLC) framework, providing a unified execution model for planning, implementation, debugging, repository evidence search, security review, scenario generation, browser automation, session logging, and other extensible engineering workflows.

For enterprise-scale projects with codebases containing millions of lines of code (LOC) and documentation repositories spanning tens of gigabytes, integration with Cortex Harness is recommended: https://github.com/baka3k/cortex-harness

The pre-configured skills provide native support for hybrid retrieval across both Graph Databases (GraphDB) and Vector Databases (VectorDB).

By combining graph-based code relationship queries with semantic vector search, the system delivers high-quality contextual retrieval, significantly accelerating project onboarding, codebase comprehension, and AI-assisted software development.

Installation

$ npx skill-dev
┌   devkit   Dev Kit Installer
│
◆  Select skills
│  ◼ hi-craft
│  ◼ hi-debug
│  ◼ hi-explorer
│  ◼ hi-fix
│  ◼ knows
│  ◼ hi-log
│  ◼ hi-plan (Should ALWAYS activate before implementing ANY implement , or fix.)
│  ◼ hi-predict
│  ◼ hi-problem-solving
│  ◼ hi-scenario
│  ◼ hi-security
│  ◼ hi-sequential-thinking
└ ....

◇ Select target agent
❯ Claude Code
  OpenCode
  Qwen Code
  GitHub Copilot
  Cursor
  Continue
  Generic

◇ Install location
❯ Global (~/.claude/skills)
  Current project

◇ Summary
Agent: Claude Code
Skills: 12 selected
Location: Global
Install? (Y/n)

Install Other skills from github

Usage

npx skill-dev                       # default: baka3/dev-kit on GitHub
npx skill-dev <url>                 # any supported source
npx skill-dev owner/repo            # GitHub shorthand
npx skill-dev ./local-skills        # local directory
npx skill-dev https://example.com   # well-known endpoint
npx skill-dev -h                    # help
npx skill-dev -v                    # version
npx skill-dev --no-manifest         # skip AGENTS.md / CLAUDE.md auto-install

Manifest files (AGENTS.md / CLAUDE.md)

Whenever the source repo (or local directory / well-known endpoint) carries AGENTS.md or CLAUDE.md at its root, skill-dev automatically copies them. Each file routes to its own "natural home" so the install mirrors how the skills directory is laid out:

File	Global scope target	Why
`AGENTS.md`	`~/.agents/AGENTS.md`	Universal, agent-neutral. Sibling of the canonical `~/.agents/skills/` so the same content is shared by every agent.
`CLAUDE.md`	`~/.claude/CLAUDE.md`	Claude-Code-specific. Sits alongside the `skills/` symlink that points into `~/.agents/skills/`. Respects `$CLAUDE_CONFIG_DIR` if set.
Other (e.g. `GEMINI.md`)	`~/.agents/` (fallback)	Unknown filenames default to the canonical `~/.agents/` — add a new switch case in `src/install/manifest.ts` to route a new manifest elsewhere.

For project scope every file lands at the project root (<cwd>/AGENTS.md, <cwd>/CLAUDE.md) — same convention as the rest of the ecosystem.

AGENTS.md

# Root Agent: Context Search Directive

**Objective:** Gather project context before executing tasks.
**Fast-Fail Rule:** If a tool is missing or disconnected -> SKIP IMMEDIATELY to the next level (Do NOT retry).

## Strict Priority Flow
*Proceed to the next step ONLY if the current step yields no results or the tool is unavailable.*

1. **`mind_mcp`**: Retrieve project docs, concepts, and foundational knowledge.
2. **`graph_mcp` (`semantic_search`)**: Find codebase relationships and logic (rely on semantics, not exact string matching).
3. **`serena` (search)**: Broad codebase search.
4. **`grep`/`rg` (Native tools)**: File system sweep for exact strings (Absolute last resort).

## Mandatory Rules
- **No Hallucination:** If the entire search chain fails, stop and ask the user for details. Never fabricate context.
- **Merge Context:** Prioritize structured data from `graph_mcp` if tools return overlapping information.
- **No Assumptions:** Ask, don't guess. Highlight tradeoffs and admit confusion.
- **Minimal Code:** Solve only the target problem. No over-engineering.
- **Strict Scope:** Touch only what's necessary. Clean up your own mess.
- **Success Criteria:** Iterate until explicitly verified.

NOTICE: For complex codebases exceeding millions of Lines of Code and massive documentation scale (tens of gigabytes), you need mind_mcp & graph_mcp - please integrate with cortex-harness (https://github.com/baka3k/cortex-harness).

mind_mcp: GraphRAG – Handles project document processing and retrieval.
graph_mcp: GraphCode – Maps the source code call graph, visualizing function-level node interactions.

About Serena - refer https://github.com/oraios/serena

Supported agents

Agent	Global install	Project install
Claude Code	`~/.claude/skills`	`.claude/skills`
OpenCode	`~/.config/opencode/skills`	`.opencode/skills`
Qwen Code	`~/.qwen/skills`	`.qwen/skills`
GitHub Copilot	`~/.copilot/skills`	`.github/skills`
Cursor	`~/.cursor/skills`	`.cursor/skills`
Continue	`~/.continue/skills`	`.continue/skills`
Generic	`~/.devkit/skills`	`.devkit/skills`

Set CLAUDE_CONFIG_DIR, CODEX_HOME, or XDG_CONFIG_HOME to override the base config directory.

What Is Included

Core Workflow Skills

Directory	Skill name	Purpose
`hi-craft/`	`hi-craft`	Feature implementation workflow: plan, implement, test, and finalize.
`hi-fix/`	`hi-fix`	Bug, test, CI, type, lint, UI, and runtime issue resolution.
`hi-plan/`	`hi-plan`	Implementation plans, architecture plans, phased roadmaps, and plan validation.
`hi-debug/`	`hi-debug`	Root-cause debugging for failures, logs, CI, databases, performance, and system behavior.

Evidence And Exploration

Directory	Skill name	Purpose
`hi-repo-search/`	`hi-repo-search`	Traceable repository evidence from project docs, semantic code search, symbols, call paths, dependency analysis, and documents.
`hi-explore/`	`hi-explorer`	Fast parallel codebase and external research for file discovery, web/docs lookup, GitHub analysis, and UI/image understanding.
`hi-knows/`	`knows`	Unified knowledge retrieval from Git, MCP, and memory files.

Analysis And Review

Directory	Skill name	Purpose
`hi-scenario/`	`hi-scenario`	Edge-case and test-scenario generation across 12 dimensions.
`hi-predict/`	`hi-predict`	Five-persona pre-analysis before risky features, refactors, or releases.
`hi-security/`	`hi-security`	STRIDE + OWASP security audit with MCP-assisted code analysis and optional iterative auto-fix.
`hi-sequential-thinking/`	`hi-sequential-thinking`	Step-by-step reasoning with revision, branching, and hypothesis testing.
`hi-problem-solving/`	`hi-problem-solving`	Structured techniques for stuck points, recurring patterns, constraints, and scale uncertainty.

Utilities

Directory	Skill name	Purpose
`hi-log/`	`hi-log`	Session log entries for recent changes, decisions, impacts, and reflections.
`hi-project-organization/`	`hi-project-organization`	File placement, output naming, directory organization, and Markdown structure.
`hi-chrome-devtools/`	`hi-chrome-devtools`	Browser automation through Puppeteer CLI scripts with persistent sessions, screenshots, performance, network, scraping, forms, auth, and debugging.
`cortex/`	`cortex`	Cortex Harness setup, project config, code/doc sync, and MCP lifecycle for graph/vector retrieval.

Repository Search Integration

hi-repo-search is the shared evidence layer for questions that require verified repository context. Use it before planning or changing code when the answer depends on codebase structure, architecture, cross-file behavior, impact analysis, or project documentation.

The expected context search chain is:

mind_mcp for project documents, concepts, and foundational knowledge.
graph_mcp semantic search for code relationships and logic.
serena search for broad codebase discovery.
rg or grep only as the final exact-string filesystem sweep.

If one level is missing or disconnected, skip immediately to the next level. If the full chain yields no evidence, stop and ask for more details instead of guessing.

hi-repo-search is intentionally evidence-only. It gathers and verifies context; orchestration remains with hi-craft, hi-fix, hi-plan, hi-debug, hi-scenario, hi-security, or the calling agent.

Recommended modes:

Mode	Use when
`--code`	You need symbol, file, call path, or implementation evidence.
`--doc`	You need project docs, concepts, requirements, or architectural notes.
`--deep`	You need to reconcile code and docs.
`--impact`	You need dependency, blast-radius, caller, or workflow impact evidence.

Installation

npx skill-dev                       # default: baka3/dev-kit on GitHub
npx skill-dev <url>                 # any supported source
npx skill-dev owner/repo            # GitHub shorthand
npx skill-dev ./local-skills        # local directory
npx skill-dev https://example.com   # well-known endpoint
npx skill-dev --no-manifest         # skip AGENTS.md / CLAUDE.md auto-install
npx skill-dev -h                    # help
npx skill-dev -v                    # version

During installation, select the skills, target agent, and install location. DevKit supports global and project-local installation.

Supported Agents

Agent	Global install	Project install
Claude Code	`~/.claude/skills`	`.claude/skills`
OpenCode	`~/.config/opencode/skills`	`.opencode/skills`
Qwen Code	`~/.qwen/skills`	`.qwen/skills`
GitHub Copilot	`~/.copilot/skills`	`.github/skills`
Cursor	`~/.cursor/skills`	`.cursor/skills`
Continue	`~/.continue/skills`	`.continue/skills`
Generic	`~/.devkit/skills`	`.devkit/skills`

Set CLAUDE_CONFIG_DIR, CODEX_HOME, or XDG_CONFIG_HOME to override base config directories where supported by the target agent.

Manifest Files

When the source repo or local directory includes AGENTS.md or CLAUDE.md, skill-dev copies those files with the installed skills.

File	Global scope target	Purpose
`AGENTS.md`	`~/.agents/AGENTS.md`	Agent-neutral operating instructions and context search priority.
`CLAUDE.md`	`~/.claude/CLAUDE.md`	Claude Code specific project instructions.
Other root manifests	`~/.agents/` fallback	Generic manifest placement for unknown agent-specific files.

For project scope, manifests land at the project root, such as <cwd>/AGENTS.md and <cwd>/CLAUDE.md.

Custom Sources

skill-dev uses source providers instead of requiring a local git clone.

Provider	Example	Notes
GitHub	`https://github.com/owner/repo`	Uses GitHub tree and raw file APIs.
GitLab	`https://gitlab.com/owner/repo`	Uses GitLab repository tree APIs.
Well-known	`https://example.com`	Reads `/.well-known/agent-skills/index.json`.
Local	`./my-skills`	Reads `SKILL.md` files from a directory tree.

A skill is any directory containing a SKILL.md with YAML frontmatter:

---
name: Code Review
description: Carefully review code for correctness, performance, and style.
---

# Code Review

Skill repositories may lay out skills under skills/, skills/.curated/, .agents/skills/, or at the repo root.

How Installation Works

For each selected skill and target agent, the installer:

Writes the skill to the canonical .agents/skills/<name> location.
Links the target agent skills directory to that canonical copy when possible.
Falls back to recursive copy on Windows or when links are unavailable.

The result is one canonical skill copy that multiple agents can consume.

Typical Workflows

Implement feature:    hi-craft -> hi-plan --fast -> implement -> test -> hi-log
Fix bug:              hi-fix -> hi-explorer -> diagnose -> fix -> verify
Plan architecture:    hi-plan --full -> hi-repo-search --deep -> phases -> validate
Investigate failure:  hi-debug -> logs/traces -> root cause -> fix recommendation
Impact analysis:      hi-repo-search --impact -> hi-predict -> scoped plan
Security audit:       hi-security -> findings -> optional auto-fix -> re-verify
Scenario coverage:    hi-scenario -> edge cases -> tests or review checklist
Browser task:         hi-chrome-devtools -> inspect/click/screenshot/network

Workflow Diagrams

Supporting Skills

Skill	Called by	Purpose
`hi-repo-search`	`hi-craft`, `hi-fix`, `hi-plan`, `hi-debug`, `hi-scenario`, `hi-security`	Evidence bundle from docs, semantic code search, symbols, call paths, and impact analysis.
`hi-explorer`	`hi-fix`, `hi-debug`, ad-hoc exploration	Parallel file discovery and external research.
`knows`	Any evidence-heavy answer	Traceable knowledge retrieval from Git, MCP, and memory.
`hi-log`	`hi-craft`, `hi-plan`, finalization flows	Session logs for changes, decisions, impacts, and reflections.
`hi-project-organization`	Any file-producing workflow	Output paths, names, directory structure, and Markdown organization.
`hi-sequential-thinking`	`hi-plan`, complex debugging, design reasoning	Step-by-step reasoning with revision and hypothesis tracking.
`hi-problem-solving`	`hi-fix`, `hi-debug`	Stuck-point techniques after failed hypotheses or complexity spirals.

Agent Spawning And Delegation

Most DevKit skills stay single-agent by default. Subagents are used only when the skill file explicitly allows delegation and the work has independent tracks, repeated failures, or a mode that asks for parallel execution.

Skill	Spawns agents?	Trigger / condition
`hi-explorer`	Yes, by design	Splits local, external, or hybrid exploration into `1-5` non-overlapping agents. Skips task registration when `<=2` agents or task tools are unavailable. Each agent has a 3-minute timeout.
`hi-craft`	Conditional	Parallel mode launches `fullstack-developer` per phase. Test failures are handled directly for attempts 1-2; attempt 3+ spawns `hi-fix`. Planner and tester agents are explicitly not spawned.
`hi-fix`	Conditional	Standard/deep modes can activate `hi-explorer` or `2-3` parallel agents. `--parallel` creates a separate task tree and spawns `fullstack-developer` per independent issue.
`hi-plan`	Conditional	`--full` spawns 1 researcher. `--hard` and `--parallel` use 2 researchers. `--two` uses 2+ researchers for competing approaches. Fast/default mode does not spawn a researcher.
`hi-debug`	Conditional	Multi-component investigations, parallel log/data collection, or CI/CD failures with 3+ possible causes may spawn parallel collection agents.
`hi-log`	Yes	Spawns a `log-writer` subagent after filtering material changes. If there is no material change, logging aborts.
`hi-repo-search`	Conditional	Does not spawn by default. Uses at most two investigators, code and documents, only when delegation is permitted and the work has independent tracks, spans 3+ subsystems, or needs independent conflict verification.

graph TD
    A["Task / workflow request"] --> B{"Delegation allowed by skill?"}
    B -->|no| C["Single-agent execution"]
    B -->|yes| D{"Independent tracks or explicit parallel mode?"}
    D -->|no| C
    D -->|yes| E["Spawn scoped subagents"]
    E --> F["Collect outputs<br/>dedupe / reconcile conflicts"]
    F --> G["Main agent owns synthesis<br/>integration and verification"]

    E --> H["hi-explorer<br/>1-5 scoped agents"]
    E --> I["hi-plan<br/>researchers by mode"]
    E --> J["hi-fix / hi-craft<br/>fullstack-developer or hi-fix escalation"]
    E --> K["hi-debug<br/>parallel evidence collection"]
    E --> L["hi-log<br/>log-writer"]
    E --> M["hi-repo-search<br/>max 2 investigators"]

    classDef decision fill:#ffe0b2,stroke:#e65100,color:#000
    classDef primary fill:#c8e6c9,stroke:#1b5e20,color:#000
    classDef delegated fill:#bbdefb,stroke:#0d47a1,color:#000
    classDef synthesis fill:#e1bee7,stroke:#6a1b9a,color:#000
    class B,D decision
    class C,G primary
    class E,H,I,J,K,L,M delegated
    class F synthesis

`hi-craft` - Feature Implementation

Mode	Context	Plan	Review	Test
default / `--fast`	Skip research	Required unless user explicitly skips planning	Skip	Yes
`--full`	Research enabled	Required unless user explicitly skips planning	Required	Yes
`--review`	Skip research	Required unless user explicitly skips planning	Required	Yes
`--auto`	Skip research	Required unless user explicitly skips planning	Auto-pass	Yes
`--no-test`	Skip research	Required unless user explicitly skips planning	Skip	No
plan path	Execute supplied plan	Supplied	As specified	Yes

graph LR
    A["User request"] --> B["hi-craft"]
    B --> C["Plan exists?<br/>hi-plan --fast if missing"]
    C --> D{"Parallel mode?"}
    D -->|no| E["Implement directly"]
    D -->|yes| P["Launch fullstack-developer<br/>per phase"]
    P --> E
    E --> F["Run proportionate checks"]
    F -->|pass| G["Finalize<br/>report / log if needed"]
    F -->|fail x1-x2| E
    F -->|fail x3+| H["Spawn hi-fix<br/>deep debug"]

    classDef primary fill:#c8e6c9,stroke:#1b5e20,color:#000
    classDef delegated fill:#bbdefb,stroke:#0d47a1,color:#000
    classDef gate fill:#ffe0b2,stroke:#e65100,color:#000
    class B,E,G primary
    class P,H delegated
    class C,D,F gate

`hi-fix` - Issue Resolution

Mode	Scope	Repository evidence	Delegation
default	1 file, type/lint, or clear issue	Direct inspection	1 agent is enough
`--standard`	2-5 files	Full explorer and diagnosis	`hi-explorer` or `2-3` parallel agents when useful
`--deep`	5+ files or architectural impact	Parallel explorer, diagnosis, and research	Parallel agents for exploration/research
`--parallel`	2+ independent issues	Separate task tree per issue	Spawn `fullstack-developer` per issue
`--review`	Any scope	Mode-dependent	Human review at gates

graph LR
    A["Capture symptom<br/>error / log / failing check"] --> B["Explore affected area"]
    B --> P{"Standard / deep / parallel?"}
    P -->|no| C["Diagnose<br/>symptom -> cause -> root cause"]
    P -->|yes| X["hi-explorer or parallel agents<br/>locate evidence"]
    X --> C
    C --> D["Fix root cause<br/>minimal change"]
    D --> E["Verify"]
    E -->|pass| F["Finalize<br/>evidence + change + verification"]
    E -->|fail x1-x2| C
    E -->|fail x3| G["Stop and question architecture"]

    classDef step fill:#bbdefb,stroke:#0d47a1,color:#000
    classDef gate fill:#ffe0b2,stroke:#e65100,color:#000
    classDef fail fill:#ffcdd2,stroke:#b71c1c,color:#000
    class A,B,C,D,F,X step
    class P,E gate
    class G fail

`hi-plan` - Implementation Planning

Mode	Research	Delegation	Review
default / `--fast`	Skip formal research; read docs or scan only if needed	None	None
`--full`	Research enabled	1 researcher	Optional red-team and validation
`--hard`	Deep research and impact analysis	2 researchers	Required red-team
`--parallel`	Parallel-track research	2 researchers	Required red-team
`--two`	Competing approaches	2+ researchers	Review after selection

graph LR
    A["Scan active plans"] --> B["Gather evidence<br/>hi-repo-search"]
    B --> R{"Research mode?"}
    R -->|fast| C["Define assumptions<br/>dependencies / gaps"]
    R -->|full / hard / parallel / two| S["Spawn researcher agents<br/>by selected mode"]
    S --> C
    C --> D["Write plan.md<br/>and phase files"]
    D --> E{"3+ phases?"}
    E -->|yes| F["Hydrate tasks"]
    E -->|no| G["Skip task overhead"]
    F --> H["Return plan path<br/>and execution command"]
    G --> H

    classDef step fill:#bbdefb,stroke:#0d47a1,color:#000
    classDef evidence fill:#e1bee7,stroke:#6a1b9a,color:#000
    classDef delegated fill:#bbdefb,stroke:#0d47a1,color:#000
    classDef gate fill:#ffe0b2,stroke:#e65100,color:#000
    class A,C,D,F,G,H step
    class B evidence
    class S delegated
    class R,E gate

Cross-Skill Integration

graph TD
    User(["User request"]) --> Detect{"Intent"}

    Detect -->|feature / implementation| Craft["hi-craft"]
    Detect -->|bug / failure| Fix["hi-fix"]
    Detect -->|plan / architecture| Plan["hi-plan"]
    Detect -->|repo question / impact| RepoSearch["hi-repo-search"]
    Detect -->|debug investigation| Debug["hi-debug"]
    Detect -->|security audit| Security["hi-security"]
    Detect -->|edge cases / tests| Scenario["hi-scenario"]
    Detect -->|browser task| Chrome["hi-chrome-devtools"]

    Craft -->|missing or stale evidence| RepoSearch
    Craft -->|plan needed| Plan
    Craft -->|verification fails repeatedly| Fix
    Craft -->|final record| Log["hi-log"]

    Fix -->|2-5 files| RepoSearch
    Fix -->|large / impact scope| RepoSearch
    Fix -->|root cause difficult| Debug
    Fix -->|2+ failed hypotheses| ProblemSolving["hi-problem-solving"]
    Fix -->|final record| Log

    Plan -->|code/doc evidence| RepoSearch
    Plan -->|complex reasoning| Sequential["hi-sequential-thinking"]
    Plan -->|outputs / naming| Org["hi-project-organization"]
    Plan -->|archive / final record| Log

    Debug -->|find files / external research| Explorer["hi-explorer"]
    Debug -->|repo evidence| RepoSearch
    Debug -->|stuck| ProblemSolving

    Security -->|code graph + policy context| RepoSearch
    Scenario -->|feature paths + business rules| RepoSearch
    RepoSearch --> Knows["knows"]

    classDef primary fill:#c8e6c9,stroke:#1b5e20,color:#000
    classDef evidence fill:#e1bee7,stroke:#6a1b9a,color:#000
    classDef analysis fill:#bbdefb,stroke:#0d47a1,color:#000
    classDef utility fill:#fff9c4,stroke:#f57f17,color:#000
    classDef external fill:#f5f5f5,stroke:#333,color:#000

    class Craft,Fix,Plan primary
    class RepoSearch,Knows evidence
    class Debug,Security,Scenario,Sequential,ProblemSolving,Explorer analysis
    class Log,Org,Chrome utility
    class User,Detect external

HARD-GATEs

Skill	HARD-GATE	Violation behavior
`hi-craft`	Do not edit until a reviewed plan exists, unless the user explicitly skips planning.	Stop, create or reuse a plan, then continue.
`hi-fix`	Do not fix before locating the failure and identifying root cause.	Return to explore/diagnose; after 3 failed fix attempts, question architecture with the user.
`hi-plan`	Scan active plans first and record relevant `blockedBy` / `blocks` relationships.	Update the related plans before producing the new plan.
`hi-repo-search`	Provide traceable evidence only; do not invent context or own implementation decisions.	Report search coverage and ask for details if evidence is missing.
`hi-security`	Security findings need source evidence and severity-ranked remediation.	Do not auto-fix outside the requested audit/fix scope.
`hi-project-organization`	Do not override established project layout without evidence.	Use existing conventions or return an advisory recommendation.

General Rules

Hard-gates first, fast path after that.
Use hi-repo-search when codebase structure, docs, relationships, or impact matter.
Prefer direct execution for small local tasks; escalate to deeper modes when risk, uncertainty, or file count grows.
Verify proportionally: quick checks for narrow edits, broader tests for shared behavior or user-facing flows.
Keep hi-repo-search as evidence gathering; orchestration and final decisions stay with the calling skill or agent.

Folder Structure

dev-kit/
├── AGENTS.md
├── CLAUDE.md
├── README.md
├── devkit.md
├── hi-cortex/
├── hi-chrome-devtools/
├── hi-craft/
├── hi-debug/
├── hi-explore/
├── hi-fix/
├── hi-knows/
├── hi-log/
├── hi-plan/
├── hi-predict/
├── hi-problem-solving/
├── hi-project-organization/
├── hi-repo-search/
├── hi-scenario/
├── hi-security/
└── hi-sequential-thinking/

Key Conventions

Evidence comes before assumptions. Prefer traceable context from mind_mcp, graph_mcp, serena, then native search.
Keep changes scoped. Skills should solve the target problem without unrelated refactors or cleanup.
Use the lightest useful mode first. Escalate to deep, review, parallel, or impact modes when risk or uncertainty justifies it.
hi-repo-search gathers evidence; implementation and final decisions stay with the orchestrating skill or agent.
Human-facing skill output may be localized by the calling agent. Technical artifacts, identifiers, paths, and commands stay precise.

Adding A Skill

Create your-skill/SKILL.md with name, description, and optional argument-hint / metadata.
Add references/ when the skill needs supporting procedures or deeper instructions.
Add scripts/ only for reusable automation that the skill should call instead of retyping.
Add agents/openai.yaml when the skill should appear in an agent picker.
Update this README when the skill changes the public catalog or workflow integration.

Reference Docs

Doc	What it contains
AGENTS.md	Root agent context-search directive and mandatory operating rules.
CLAUDE.md	Claude Code specific project instructions.
devkit.md	Detailed workflow diagrams and cross-skill integration notes.

License

This project is licensed under the MIT License. See LICENSE for details.

Name		Name	Last commit message	Last commit date
Latest commit History 51 Commits
hi-chrome-devtools		hi-chrome-devtools
hi-cortex		hi-cortex
hi-craft		hi-craft
hi-debug		hi-debug
hi-explore		hi-explore
hi-fix		hi-fix
hi-knows		hi-knows
hi-log		hi-log
hi-plan		hi-plan
hi-predict		hi-predict
hi-problem-solving		hi-problem-solving
hi-project-organization		hi-project-organization
hi-repo-search		hi-repo-search
hi-reverse		hi-reverse
hi-scenario		hi-scenario
hi-security		hi-security
hi-sequential-thinking		hi-sequential-thinking
.cursorrules		.cursorrules
.gitignore		.gitignore
AGENTS.md		AGENTS.md
CLAUDE.md		CLAUDE.md
LICENSE		LICENSE
README.md		README.md
devkit.md		devkit.md

Folders and files

Latest commit

History

Repository files navigation

DevKit

Advanced Capabilities

Installation

Install Other skills from github

Usage

Manifest files (AGENTS.md / CLAUDE.md)

AGENTS.md

Supported agents

What Is Included

Core Workflow Skills

Evidence And Exploration

Analysis And Review

Utilities

Repository Search Integration

Installation

Supported Agents

Manifest Files

Custom Sources

How Installation Works

Typical Workflows

Workflow Diagrams

Supporting Skills

Agent Spawning And Delegation

hi-craft - Feature Implementation

hi-fix - Issue Resolution

hi-plan - Implementation Planning

Cross-Skill Integration

HARD-GATEs

General Rules

Folder Structure

Key Conventions

Adding A Skill

Reference Docs

License

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

`hi-craft` - Feature Implementation

`hi-fix` - Issue Resolution

`hi-plan` - Implementation Planning

Packages