cycstack

Plugin cycstack from marketplace cycstack in TheDThompsonDev/cyc-stack. Commands read from the repo's manifest — 4 days ago.

Skills (19)

• cyc-build

  Implement planned behavior in thin tested slices, preserve affected consumers and hand current evidence to Verify.

• cyc-challenge

  Attack a plan, change, or claim to find what would actually break it, and return a short list of findings worth acting on. Use before committing to a consequential design, before accepting a feature, after two failed fixes, or when the user says \"poke holes\", \"review this\", or \"what am I missin

• cyc-context

  Retrieve focused feature/component knowledge and retain changes in the target project's indexed context before final verification. Use when changing, explaining or resuming a feature; completed-run catch-up requires a new scoped update.

• cyc-correct

  Turn user feedback or a repeated miss into a named missing criterion and a targeted fix, instead of another variant. Use when the user says \"that's not it\", \"still wrong\", or \"this feels off\", when a revision misses the same way twice, or when feedback reveals an unstated requirement.

• cyc-deliver

  Deliver the result first with a useful visual, traceable evidence and honest limits.

• cyc-design

  Choose the shape of a change (data, interfaces, and the steps to build it) before writing logic. Use before any change that adds state, changes a data shape or interface, spans several files, or after a build shows the current design is wrong.

• frontend-design

  Build web interfaces a reviewer cannot mistake for a default AI page. Three gates: a written design decision sheet before any markup, the signature section rendered and scored against the generic-tells list before the page is extended, and a set-divergence table when several sites are requested. Use

• cyc-error-ledger

  Retain searchable failure history with causes, attempted fixes, results and regression evidence. Use when diagnosing a reported bug, error or log, when an attempted fix fails, and when recording its resolution.

• cyc-explore

  Settle an open decision by comparing genuinely different options or building a throwaway prototype, then recommend one. Use when the user asks \"which approach\", \"what are my options\", or \"what should this look like\", when earlier options were rejected, or when a design fork would be expensive

• cyc-frame

  Turn a request into a destination, scope, and acceptance criteria someone could check, interviewing the user only on real decisions. Use at the start of a task, when the request is vague, or when feedback shows the goal was misunderstood.

• cyc-impact

  Find what a change could break beyond the lines it edits, and prove the fact that makes it safe. Use before any substantive change, when a change touches shared state, storage, or interfaces, or when a build or verify step reveals an unexpected dependency.

• cyc-reflect

  Turn what went wrong or right in finished work into specific proposed edits to CYC skills, checks, or project rules, each tied to evidence. Use when the user says \"reflect\", \"what did we learn\", or \"improve the workflow\", after a task needed corrections, or when a missed dependency or repeated

• cyc-remember

  Keep a running decision log during work and rebuild context when resuming, so the next session knows what was decided, why, and what's next. Use at checkpoints, before stopping mid-task, when the user says \"catch me up\" or \"where did I leave off\", or when handing work to another session or tool.

• cyc-scout

  Establish affected behavior, consumers, checks and a short implementation plan before editing; for advisory work, establish the explanation/review scope without assuming edit permission.

• cyc-setup

  Set up CYC in the current project: activate it, find the project's real test, lint, and type-check commands, write them into the CYC config, and confirm everything works. Use when the user says \"set up cyc\", \"activate cyc\", \"install cyc here\", or right after installing the CYC plugin.

• cyc-teach

  Teach a concept through the learner's own project with a plain definition, a worked example from their code, and a small practice task. Use when the user says \"explain\", \"teach me\", \"help me understand\", \"why does this work\", or is a student or newer developer learning while building.

• cyc-understand

  Build an evidence-backed model of how the existing system behaves, or reproduce and locate a failure. Use for \"how does X work\", \"why does X happen\", bug reports, anything broken, throwing, or slow, and before designing a change to unfamiliar code.

• cyc-verify

  Prove the requested change works and nothing it touches broke, using checks you actually ran against the current files. Use before accepting any change, when asked \"does it work?\", after a repair, or when a handoff claims success.

• cyc

  Run a software task through CYC: a fast scout, a build, and a verify loop that repeats until the project's real checks pass, then a concise handoff. Use when the user says \"cyc\", \"run this through cyc\", or, in a project with CYC installed, asks for a feature, bug fix, refactor, performance impro

Similar plugins