nextc-core

Plugin nextc-core from marketplace nextc-claude in nextc/nextc-claude. Commands read from the repo's manifest — 5 days ago.

Skills (10)

• autopilot

  Carry out an approved plan without the user, then report every question, answer and decision made along the way. Use when the user wants a plan executed unattended, "autopilot", or "run this plan without me".

• blueprint

  Turn a one-line objective into a cold-start-executable, multi-PR construction plan for work that spans several sessions or agents. Use when a task is too big for one PR or one session.

• bug-fix

  Evidence-driven bug investigation and fix pipeline. Use when something is broken, not working, or the root cause is ambiguous.

• clarify

  Socratic requirements gathering with ambiguity scoring. Use when the user has a vague idea, wants help thinking through requirements, or when a task is too unclear to implement directly. Interviews the user to produce a clear spec.

• cleanup

  Bounded, regression-safe code cleanup with deletion-first workflow. Use after a coding session that left dead code, duplicates, over-abstraction, or bloat. Also use when the user says "clean up", "simplify", or "remove cruft".

• feature-dev

  Full feature pipeline — idea to committed code. Use when building a new feature, adding functionality, or implementing from specs.

• finishing-branch

  Decide how to integrate completed branch work, with safe worktree cleanup. Use when implementation on a branch is complete and verified and you need to decide what happens to it.

• interface-polish

  Apply concrete design-engineering details that make a web UI feel polished. Use when a web or CSS interface feels off, flat, cramped, or unfinished.

• team-feature-dev

  Team-orchestrated feature development with parallel specialist agents. Use when building a feature that benefits from multiple agents working concurrently. You act as Product Director coordinating the team.

• update-docs

  Sync project docs with the current codebase state. Use when you have completed features, fixing bugs, or making changes that affect documentation.

Subagents (3)

• autopilot-decider

  Answers the questions an autopilot run would otherwise ask the user, so an approved plan can finish unattended. Spawned only by the autopilot skill's run mode, with the approved plan, the question and the decisions made so far.

• doc-keeper

  Updates project docs to match real codebase state. Spawn ONLY with the user's explicit approval — via /update-docs or after the user accepts a suggestion at a completion point (feature built, milestone done, fix confirmed), or once at the end of an approved /autopilot run. Never auto-spawn. Reads gi

• ui-ux-developer

  UI/UX implementation specialist that translates design assets and design.md into production code. Strictly follows approved designs for core screens and creatively implements non-core screens within the design system. Always leverages installed design skills (e.g. `ui-ux-pro-max`) when available — f

Similar plugins