All authors
Claude Skills by Ovich
github.com/Ovich35 skills0 installs82 views
- BrainstormUse when a person wants to think an idea through and keep the discussion: a feature, a tool choice, an architecture question, before a plan or without one, with the agent through an interview. Produces a board in aiview holding the decisions, the diagrams and what was investigated. Not for a swarm of seats working it (brainswarm), not for an implementation plan and not for bug fixes.Votes: 0GitHub stars: 14
- BrainswarmUse when a person wants a swarm of role seats to work a topic on the swarm board under a chosen protocol: a brainstorm (ideas before any judgment), a debate (questions argued to decisions, a skeptic endorsing) or an editorial (one text drafted, read by seats standing for its readers, revised), a protocol or template the project keeps as a `protocol-<name>` skill (or an older `brainswarm-<name>` one), or a custom protocol recommended for the person's intent, or a seat's brief names a brainswar...Votes: 0GitHub stars: 14
- InterviewUse when a person says "interview me" or asks to be interviewed about an idea or an existing design document (a board, a plan, a change) until it is understood the same way by them and the agent, or when another skill needs open decisions resolved one by one. Runs in chat and leaves the resolved decisions there, for the caller to write where they belong. Keeping the discussion as a document is brainstorm's, turning it into a plan is write-plan's.Votes: 0GitHub stars: 14
- Whiteboard DefenseUse when a person wants to be questioned about a system they shipped, says \"defend <feature>\" or \"whiteboard me on <subsystem>\", or wants to be ready to explain and defend a design to anyone who pulls them aside. Hard questions on the system and on its stack, open-book. Produces a defense report: the gaps, the reading that closes them, and the architecture leads the questions turned up. Not a review of the code, not a test of the person, not a quiz on names and lines, and it changes nothi...Votes: 0GitHub stars: 14
- Complexity ReworkUse when code is hard to follow and is to be audited or reworked: long if/else or switch chains, cascades of type checks or parse attempts, kind fields compared to strings, flag parameters, deep nesting, a function hard to read. Also for complexity guardrails, or one long conditional function pasted. Produces a ranked audit of families, one family reworked behind characterization tests, or the guardrails.Votes: 0GitHub stars: 14
- Deepen ModuleUse when a person asks to design a new module's interface or to rework an existing module so that it hides much behind little, in any tier (backend, frontend, test support, tooling), or says a module's callers know too much about it. Produces a module document in aiview, how a caller uses it, its one public entry point as signatures, what stays outside and the gap from today, discussed with the person until agreed. Not for writing the task that carries the rework out (orchestrate's tasks) and...Votes: 0GitHub stars: 14
- Dependency GraphUse when a JavaScript or TypeScript project's dependencies must be seen as they are in the code: the whole graph, what one module depends on, who depends on it, or its neighbourhood, at file or folder level. Produces a Mermaid graph document in aiview, parsed by a deterministic script, never inferred. Not for designing a module's interface (deepen-module).Votes: 0GitHub stars: 14
- Write DiagramsUse when a document produced in this collection (board, plan, report, analysis, durable doc) could carry a diagram, or when a design question would settle faster shown than said. Picks the diagram that answers the open question and holds the discipline that keeps a diagram readable. Not for decoration: no open question, no diagram.Votes: 0GitHub stars: 14
- AiviewUse whenever a document is produced for the user to read and react to while it evolves: a brainstorm board, a plan, a design language, a prototype, a PR analysis, a review report, a live PDF. Also when a document must be registered, opened, listed, moved or retired, or a prototype's bindings checked. Not for code, tests or configuration, or any file nobody opens in a browser.Votes: 0GitHub stars: 14
- Swarm BoardUse when agents run together on the project's swarm board: a plan, a task swarm or a brainswarm, as its orchestrator or a member whose brief names a run, or when a run on the board has to be opened, read, interrupted or closed. Produces nothing but the run's state on the board. Not for documents (aiview).Votes: 0GitHub stars: 14
- Execute PlanUse when carrying out an implementation plan the person has already approved, whether starting it or resuming it in a later session, and the tracker in it has to stay true while the work happens. Not for producing the plan (write-plan) and not for reviewing the result.Votes: 0GitHub stars: 14
- Orchestrate PlanUse whenever execute-plan runs, as the plan's orchestrator: settling the mandate, running the plan phase by phase on the swarm board, dispatching the plan's workers once, posting each phase's tasks to them, watching the board, verifying merges, and handling the branch and pull request. Not for keeping the tracker or deciding when to pause (execute-plan), and not for doing a task (the swarm-worker agent).Votes: 0GitHub stars: 14
- HelpUse whenever the person needs to understand what is going on in this collection: they ask (how something works, what a term or a verb's answer means, what is happening in a run, what can be done here, how to start), they call help, or, unasked, the moment you notice they do not know or do not understand something of this ecosystem (a term they misuse or ask about, surprise at what a run or a skill does, a choice they cannot make for lack of the picture). Explains, in simple terms, what you ar...Votes: 0GitHub stars: 14
- Next StepUse at every point of a conversation where one of this collection's skills would serve the person better than going on as is, and they have not named it: an idea still vague or choices left open (offer the interview), decisions worth keeping (a brainstorm board), agreement on something to build (a plan, or a swarm with its protocol filled in), a question to decide or a text to write from several viewpoints (a brainswarm), a run that just closed (its follow-up). Produces one offer in one line;...Votes: 0GitHub stars: 14
- OrchestrateUse when an agent orchestrates other agents on a piece of work, of any kind (a plan, a task swarm, a brainswarm): proposing a run tuned to the work, built on the closest protocol (build-verify, idea-to-outcome, brainstorm, debate, editorial, a project's own), settling it with the person, dispatching each member with its brief and role, watching them, judging their findings and steering a drift. Not for the duties one kind adds (orchestrate-plan for a plan, swarm for a task swarm, brainswarm f...Votes: 0GitHub stars: 14
- Cold ReadUse when dispatched to cold-read a plan, as an agent that was not in the conversation that wrote it, to say whether it can be carried out from the document alone. Produces what the reader would build, its questions, and a verdict, ready or not ready, repeated as the writer fixes the plan. Not for judging the design (interview, pr-review), not for the mechanical checks (aiview plan check, tracker check), and not for writing the plan (write-plan).Votes: 0GitHub stars: 14
- Write PlanUse when something non-trivial is to be built or reworked and its implementation plan has to be written, from an idea or from a board, or when a plan has to be redrawn after an increment landed. Produces, through an interview, the one plan document that holds the design, the decisions, the phases and seats, the tracker execute-plan runs from and the orchestrator's mandate. Not for keeping an open discussion (brainstorm), not for writing a phase's tasks (orchestrate-plan, at the phase's open) ...Votes: 0GitHub stars: 14
- RoadmapUse when a project has to be declared above its pieces of work, from nothing or from the boards, plans and prototypes already made, when a slot has landed or the picture has changed and the roadmap must be redrawn, or when someone asks where the project stands. Produces and keeps the roadmap (iterations of deliverable slots, each slot's state derived from what exists for it) and the foundation reference (the technology decisions). Not for designing a slot (brainstorm), planning it (write-plan...Votes: 0GitHub stars: 14
- Technical WritingUse when the work produces a document that must be understood by someone who was not there when the system, procedure or decision was made, and that stays in the repository after the work merges: a README, an architecture or system document, an ADR, a runbook, an onboarding guide, an API guide, a migration note. Not for the working documents of a piece of work (boards, specs, plans and reports belong to the skills that produce them) and not for persuasive prose.Votes: 0GitHub stars: 14
- Write ConventionsUse when a project's conventions need to be written down or extended: starting a codebase from scratch, settling how one tier uses its framework, capturing a design decision that was just made, or turning unwritten patterns in an existing repo into rules. Produces or grows an AGENTS.md / CLAUDE.md. Any language or stack.Votes: 0GitHub stars: 14
- Pr ReviewUse when reviewing a pull request, branch or diff in any language, to produce the analysis a reviewer decides from: what changed, why, how the structure moved, what it can break, and the decisions only a human can make, at five altitudes from code primitives to delivery and intent. Not a bug hunt, and not framework-specific review.Votes: 0GitHub stars: 14
- Recurring Review FindingsUse when the same remark keeps being made in a repository's pull request reviews, or when someone asks what the reviews keep catching and how to stop catching it. Groups the comment history into recurring findings and decides, for each, the rung that removes it: a design that makes it impossible, a lint or type rule, a test in CI, a convention, a fix to the skill that produced the code. Produces a report in aiview with a recommendation per finding, applied on a yes. Not for reviewing one pull...Votes: 0GitHub stars: 14
- SwarmUse when a person asks to swarm, delegate or parallelize work without a plan ('swarm this', 'run a swarm on…', 'get a few agents on it'), or when a task in front of you splits into independent parts or is long enough to hand off: then propose a swarm in one line, workers and why, and open it only on a yes. Runs a task swarm on the board: this session orchestrates, N swarm-worker agents take the tasks posted to them, report, and take the next, for as long as the person keeps giving work, on ca...Votes: 0GitHub stars: 14
- Design PrototypeUse before building or changing any screen (a new page, dialog, panel, or a visual rework), to design it first as a prototype in the project's own design language, which the skill extracts from the codebase and writes down once. Not for implementing the screen and not for reviewing its code.Votes: 0GitHub stars: 14
- Point AtUse when about to ask the person a question, answer one of theirs, or explain something to them, about a screen, a region or a component of the interface: in an interview, a plan, a board, a review or plain chat. Also when the person says they do not see what is meant on a screen. Finds the screen's prototype and points the person's viewer at the components concerned, so the question or the answer is given in the prototype's own names with the thing lit in front of them. Not for designing or ...Votes: 0GitHub stars: 14
- Validate DeliveryUse when the person and the agent go over what was just delivered together, live: on execute-plan's recommendation at a plan's close, or whenever the person asks to walk or rework a delivery with the agent. Runs the project's verify skill with the person guiding it, judging and deciding, the agent proposing what to check. Not for the agent's quality pass alone (the project's verify skill).Votes: 0GitHub stars: 14
- Verification Skill CreateUse when a project has no verifier for a focus (what is judged, through what) and an agent should from now on judge, alone, the product quality of what is delivered (done as specified, usable, finished): on request, or from the mandate questions of orchestrate-plan when the person says yes. Produces the project's `verify-<app>-<focus>` skill, proven by one quality pass. Not for a focus that has one (its verify skill adapts itself), running a pass (the project's verify skill), tests, code qual...Votes: 0GitHub stars: 14
- Create WorkbenchUse when a page is wanted to work on something with the person during development, fed the project's real data (comparing model answers, walking an agent call by call, measuring an output against its template), when such a workbench has to change, be reworked or its feed broke, or mid-session when turns went into aligning with the person on how to do a kind of work that recurs and real project data could show it. Produces the page in aiview, kind `workbench`, and the project's `workbench-<ben...Votes: 0GitHub stars: 14
- Create WorkbenchThe bench skill records how the work is done: what the person and the agent aligned on, kept so it is never explained again, with the bench as its dev tool. Text in `[brackets]` is filled from the definition. Every other sentence is carried as written. ```markdown --- name: workbench-[bench] description: "Use when [the bench's scope, a kind of work on a part of the product] is to be worked on with the person on the [label] workbench, or the bench's feed or scripts fail. Feeds the page from th...Votes: 0GitHub stars: 14
- Simplify ReworkUse when a whole codebase has grown by accretion and is to be audited or cut back, with no commit range to start from: superseded paths left behind by past shifts, unused exports and files, two implementations of one concern, or the person asks where the dead code is, to clean up the repo, or to stop it coming back. Produces a ranked audit of families, each approved family cut back through the simplify skill, and the guard. Not for the code one piece of work changed (simplify), branching comp...Votes: 0GitHub stars: 14
- SimplifyUse when the code a piece of work changed is to be cut back to fewer lines, behaviour unchanged: a commit range (`<base>..<head>`) whose changes left old paths, unused code or a second implementation behind, a path the work just replaced, one family handed over by a simplify-rework audit, or a run's simplify phase. Produces each superseded path deleted and each duplicate consolidated, one narrow pass each, tests green, net lines negative, and a short summary. Not for auditing a whole codebase...Votes: 0GitHub stars: 14
- Long HorizonUse when work on one subject runs over many sessions and iterations, with verifiers and the person judging as it goes, and must be stoppable at any moment and resumed by a fresh session the next day, or when the person or a brief asks to keep, resume or tick a long-horizon document. Produces and keeps that document in aiview, kind `long-horizon`: a summary and a list of elements, each with its status, owner, last check and evidence. Not for a plan's phases and tracker (write-plan, execute-pla...Votes: 0GitHub stars: 14
- Guide ComplexityUse when code is written or changed that branches heavily, in any language: if/else or switch chains, type-check cascades, kind fields compared to strings, flag parameters, deep nesting. Produces the branching shaped before it lands, and the bar it must meet at merge. Not for auditing or reworking existing code (complexity-rework).Votes: 0GitHub stars: 14
- Guide CreateUse when a project needs a guide of its own: a rule for how a kind of code is shaped while written, scoped to the files it governs. Produces the project's `guide-<name>` skill at `<repo>/.claude/skills/guide-<name>/SKILL.md`. Not for a repository-wide convention (write-conventions) and not for a skill that does work (write-skills).Votes: 0GitHub stars: 14
- Guide Deepen ModuleUse when code is written or changed that adds a module or changes a module's public interface, in any tier. Produces an interface shaped before the code behind it, and the bar it must meet at merge. Not for designing the interface with the person (deepen-module) and not for code that leaves every interface as it was.Votes: 0GitHub stars: 14