solo-code-harness-core

Plugin solo-code-harness-core from marketplace solo-code-harness in meldkin/Solo-Code-Harness. Commands read from the repo's manifest — 1 month ago.

Skills (63)

• agent-md-refactor

  Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation. category: development source: repository: 'https://github.com/softaworks/agent-toolkit' path: skills/agent-md-refactor

• algorithmic-discipline

  Bắt buộc khai báo độ phức tạp Big-O và cấu trúc dữ liệu trước khi viết thuật toán.

• api-patterns

  Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

• block-no-verify

  Prevent commits that skip pre-commit hooks (--no-verify, -n). Auto-loads when git commit with bypass flags is attempted. Triggers: commit --no-verify, git commit -n, git push --no-verify.

• brainstorming

  Explore ideas before implementation, design features, make architecture decisions, and validate approaches. Use when: brainstorm, explore options, design, what approach, how should we, ideas, before building.

• browser-testing-with-devtools

  Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MC

• ci-cd-and-automation

  Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines.

• claude-api

  Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any fo

• code-review-expert

  Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

• codebase-design

  Shared vocabulary for designing deep modules. Use when: design a module interface, decide where a seam goes, make code more testable, reduce coupling, evaluate if a module is too shallow, or another skill needs the deep-module vocabulary.

• context-engineering

  Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

• custom-deploy-workflow

  Project inspection and deployment preparation workflow for staging/production. Use when: prepare deploy, deploy project, release version, check deploy.

• debugging-and-error-recovery

  Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

• deprecation-and-migration

  Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

• documentation-and-adrs

  Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

• domain-modeling

  Build and sharpen a project's shared language (glossary) in CONTEXT.md. Use when: terms are ambiguous, the same concept has multiple names, naming a new module/concept, onboarding to a fuzzy domain, or output is too verbose because no shared vocabulary exists.

• doubt-driven-development

  Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be che

• file-editor-pro

  Edit files, modify source code, fix bugs, refactor, and apply precise code changes safely. Use when: edit file, fix this, modify, replace, update code, apply changes.

• frontend-ui-engineering

  Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

• gemini-delegation

  Routes read-heavy work, broad scoped changes, and independent review to Gemini through the Antigravity headless CLI, selecting gemini-3.8-flash high/medium/low by task complexity. Use GUI inbox/outbox handoff only when a rendered UI needs human verification.

• git-workflow-master

  Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

• handoff

  Compact the current conversation into a handoff document so a fresh agent or next session can continue. Use when: hand off, end of session, context getting full, switch agents, pause work, write a handoff.

• idea-refine

  Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on \"ideate\", \"refine

• improve-codebase-architecture

  Scan a codebase for deepening opportunities — refactors that turn shallow modules into deep ones — and present ranked candidates. Use when: architecture review, codebase feels like a ball of mud, too many small modules, hard to test, reduce coupling, improve maintainability.

• incident-investigation

  Investigate a production incident, error spike, or log/data anomaly under time pressure -- find root cause before proposing a fix. Use when: production down, incident, outage, error spike, logs, investigate production, on-call, something broke in prod.

• incremental-implementation

  Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

• interview-me

  Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified (\"build me X\" without \"for whom\" or \"why now\"), when the user explicitl

• mcp-builder

  Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

• mcp-integrator

  Dynamically enable, disable, and suggest MCP servers based on task needs. Use when: install MCP, add tool, enable browser, playwright, web search, database access, github MCP, suggest tools.

• observability-and-instrumentation

  Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the availabl

• performance-optimization

  Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

• permission-guard

  Guard destructive operations. Use when: delete, rm, remove, drop, truncate, credentials, config change, bulk edit.

• plan

  Plan mode: write an actionable markdown plan to .kilo/plans/, no execution. Bite-sized tasks, exact paths, complete code.

• planning-and-task-breakdown

  Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks.

• requesting-code-review

  Pre-commit review: security scan, quality gates, auto-fix.

• research

  Investigate a question against high-trust primary sources and capture the findings as a cited Markdown file. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background sub-agent.

• resolving-merge-conflicts

  Resolve in-progress git merge or rebase conflicts systematically. Use when you hit conflicts during merge, rebase, or cherry-pick.

• security-and-hardening

  Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

• shipping-and-launch

  Prepares production launches. Use when preparing to deploy to production.

• simplify-code

  Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

• solo-code-harness

  Deploy, configure, and maintain the Solo-Code multi-agent harness across Copilot, Claude, Gemini, and Kilo. Use when: deploy harness, setup copilot, setup claude, setup gemini, setup kilo, configure AI agents, install AI harness, solo-code setup, initialize project.

• source-driven-development

  Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

• spec-driven-development

  Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet.

• spike

  Throwaway experiments to validate an idea before build.

• steering-and-course-correction

  Correct an agent's direction mid-task without derailing progress -- when it scopes too broadly, misreads intent, or drifts from the actual goal. Use when: wrong direction, off track, not what I meant, too much, scope creep, redo, narrow down, that's not it.

• subagent-driven-development

  Execute plans via task subagents (2-stage review).

• systematic-debugging

  Diagnose bugs, test failures, unexpected behavior, and errors before proposing fixes. Use when: debug, bug, error, failure, unexpected, broken, not working, investigate, root cause.

• task-delegation

  Analyze tasks for parallel execution, spawn sub-agents via agent_manager, and merge results. Use when: parallel tasks, delegate work, spawn sub-agent, run tasks in background, split work, multi-agent.

• testing-patterns

  Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

• ui-mock-hunter

  Truy tìm và loại bỏ các dữ liệu fix cứng (hardcode) hoặc mock data trên giao diện UI để đảm bảo kết nối API thực.

• using-agent-skills

  Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

• wayfinder

  Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets. Chart the route through fog, resolve one ticket per session, until the way to the destination is clear.

• writing-great-skills

  Reference for authoring and editing skills in this harness. Use when: create skill, edit skill, write SKILL.md, improve a skill, skill too long, skill not triggering, add a new capability to the harness.

• api-providers
• custom-framework-rules
• harness-boundaries
• harness-checklist
• rules-database
• rules-git
• rules-python
• rules-typescript
• security-patterns
• shared-state

MCP servers (4)

• sequential-thinking

  runs: npx -y @modelcontextprotocol/server-sequential-thinking

• memory

  runs: npx -y @modelcontextprotocol/server-memory

• context7

  runs: npx -y @upstash/context7-mcp@latest

• playwright

  runs: npx -y @playwright/mcp

Similar plugins