All authors

Claude Skills by greenfield-inc
github.com/greenfield-inc168 skills21 installs234 views
- BriefUse when a problem, idea, or change of intent is worth capturing as a long-form page, or the person asks to write it up. Never chooses a solution; the tracker issue belongs to create-ticket.Votes: 0GitHub stars: 661
- Bug IntakeUse when the person reports broken behaviour or starts a session to file a bug. Reproduces and reports. Never fixes.Votes: 0GitHub stars: 661
- Codebase ExplorerExplore the codebase to locate files, trace behavior, and document existing patterns with precise file references. Use when the task is understanding what exists, not proposing changes.Votes: 0GitHub stars: 661
- Cold ReadGive a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process, instructions, code. It reports what's broken, confusing, or contradictory. A fresh perspective on something before it ships - especially useful on a PR you think is finished, or any user-facing artifact. Always dispatch as a fresh sub-agent with no conversation history - the zero context is the point.Votes: 0GitHub stars: 661
- Create TicketCapture work and evolving intent during discussion as one or more GitHub tickets, published briefs, or both. Use for ticket or issue creation, follow-ups, backlog capture, delegation, and revisions as decisions change. Preserve the what, why, outcome, scope, and acceptance criteria.Votes: 0GitHub stars: 661
- DiscussionHave an interactive discussion about a topic, approach, feature, or bug without making code changes. Researches the codebase as needed and talks through options. Use to think through an approach before planning or coding.Votes: 0GitHub stars: 661
- Eli5Teach an unfamiliar topic from first principles with a picture-first HTML explanation, published to the workspace's document destination when one is named. Use for "explain from scratch," "I'm lost," "what does this mean?", "explain in plain English," beginner questions about how something works, or /eli5; no explicit skill invocation is needed. Skip simple factual lookups and respect text-only requests.Votes: 0GitHub stars: 661
- Excalidraw Pr DiagramsDraw Excalidraw diagrams that make a visual argument, such as a pull request's before/after visual overview, an architecture, a workflow or a shareable explainer, then render them to PNG and check them by eye.Votes: 0GitHub stars: 661
- Explain VisuallyComplement an answer or discussion with a first-principles visual HTML explanation, published to the workspace's document destination when one is named. Use when explaining how something works, why it changes, or how options differ and a visual would materially help understanding, including requests like "show me" or "help me understand." Skip simple factual answers and text-only requests.Votes: 0GitHub stars: 661
- ExplainUse when the person wants to understand a concept or how something works today. Never plans.Votes: 0GitHub stars: 661
- Gather EvidenceUse when handed one factual question about the code or a running system. Returns evidence. Never proposes a fix.Votes: 0GitHub stars: 661
- Html ExplainerThe house standard for any skill that renders an HTML page for a person to read, covering design tokens, typography, components, diagrams, and quality gates so every generated page shares one calm, graphic-first look. Use when a skill's instructions say to render its output per the html-explainer standards, or when the user asks for an HTML explainer of anything and no more specific skill applies.Votes: 0GitHub stars: 661
- InvestigateInvestigate a bug or broken behavior through hypothesis-driven root cause analysis and report what is wrong without jumping straight to a fix. Use when something is failing or behaving unexpectedly.Votes: 0GitHub stars: 661
- OptionsUse when the person asks what to do or for trade-offs, or more than one design is live. Waits for a pick. Never plans.Votes: 0GitHub stars: 661
- PageHouse standard for any HTML page written for a person. Use when another skill says to render a page.Votes: 0GitHub stars: 661
- Pane WorkAnswer questions about the user's own work in Pane, read-only. Recap what they worked on, finished, or shipped over a time window, or rank what to do next across panes, pull requests, issues, checks, and reviews. Use for "what have I been working on?", "what did I finish yesterday?", "what should I work on next?", "which PRs are closest to shipping?", or "what should I ignore for now?".Votes: 0GitHub stars: 661
- Pr Test AutomationRun first-pass automated manual testing for PRs that are reviewed or nearly ready to merge. Use when the user asks to test a PR/branch/worktree, validate product flows, exercise browser or CLI workflows, map changed UI journeys with screenshots, verify analytics/webhooks/payments/email/SMS behavior through connected tools, or produce manual QA notes before human testing.Votes: 0GitHub stars: 661
- Prepare PrPrepare a branch for review by committing scoped changes, rebasing on main, running builds, and creating or updating a pull request. Use when the user wants the branch ready for PR review. Also use for rewriting an existing PR description from its current diff and evidence.Votes: 0GitHub stars: 661
- Quick VerifyUse while working to confirm a change does what you meant before moving on. Observe its real effect the way a user or caller would, compare that with your intent, fix what is off, and observe again.Votes: 0GitHub stars: 661
- RefactorQuality pass on a branch against its remote default branch. Runs a simple analysis (conventions and smells) and, on large changes, a deep one (correctness defects) as blind, independent subagents, merges them once, stops for the person, then applies the approved plan and has an adversary try to break it. Use after a PR is open, or when asked to refactor, clean up or quality-check a branch. Modes - simple, deep, apply - can also run alone.Votes: 0GitHub stars: 661
- ReviewReview a PR against its linked issue, repository checks, correctness, architecture, and applicable conventions. Post structured findings as a PR review.Votes: 0GitHub stars: 661
- Rewrite Simply(foundational) Answer first, cut clutter, keep the human in it. The structural layer above line-level editing, and the standing default for anything a person reads.Votes: 0GitHub stars: 661
- Session TracePublish agent sessions as readable trace pages in the workspace's document destination, with the story, key moments, every request and step on a timeline, subagents, and the pull requests it opened. Use when asked for a trace or "how did this run go", when a task already has a published page (for example from prepare-pr or handoff), or when an orchestrator collects the traces of a Session.Votes: 0GitHub stars: 661
- Smallest TestTurn a consequential uncertainty into the cheapest meaningful test before committing to an approach. Use for "how could we test this?", "is this worth building?", or choosing a small experiment to resolve an assumption.Votes: 0GitHub stars: 661
- SpikeUse only when a decision is blocked on a fact nobody has. One time-boxed question, one answer.Votes: 0GitHub stars: 661
- TddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Votes: 0GitHub stars: 661
- Ui MockupCreate three UI mockup options per round, then refine the person's favourite into the approved design reference. Works from screenshots of the current product or from agreed references for something new, with whatever tools are available (an image model, HTML and CSS in a browser, or a wireframe). Use for "mock this up," "UI mockup," or "show me what this would look like" before an interface is built. Saves the approved design with the ticket, brief or plan.Votes: 0GitHub stars: 661
- Verify AppUse when behaviour must be proven in the running application: journeys, screenshots for visual checks, external effects, or reproducing a bug. Never fixes.Votes: 0GitHub stars: 661
- Research WebPerform technical web research using authoritative sources, synthesize the results, and save a cited research note in the repo. Use when external documentation or up-to-date behavior matters, or when handed one question the codebase cannot answer.Votes: 0GitHub stars: 661
- Pane Manage And Message AgentsUse when the user asks to start, kick off, spawn, check on, nudge, follow up with, or babysit another coding agent (Claude, Codex, or Cursor) in Pane, or to create a Pane for that work.Votes: 0GitHub stars: 661
- Migrate To PaneBring the agent sessions a person already has (Claude Code, Codex, OpenCode, Cursor, Conductor, or any similar tool) into Pane, each opened in a Pane tab with its own agent's resume, verified, grouped into Sessions, and ending in a Start here page. Use for "migrate to Pane", "bring my sessions into Pane", "import my Claude/Codex/Cursor chats", when the Onboarding Session's first prompt says the person said Yes on Pane's first-run screen, or when it asks for a Start here page without a migration.Votes: 0GitHub stars: 661
- Pane AutopilotHow Pane's Autopilot works - the always-running agent above every Session that analyzes every Session and waiting item, proposes workstreams in a sensible order, drives the conversation without waiting to be told what's next, walks the Sessions, puts what waits on the person in front of them on its stack with their documents, writes its own documents and approvals in its run folder, relays the person's questions and instructions to orchestrators, and proposes close-out. It surfaces approvals ...Votes: 0GitHub stars: 661
- Pane OrchestrationHow any orchestrator drives worker agents through Pane with the runpane CLI - one Pane per feature, launching a worker as a new Pane or tab (built-in agents or a wrapper --tool-command such as agent-farm run), the one wait primitive, worker reports and status files, answering workers, resuming after a restart or sleep, showing pages beside the person, shared-checkout and port etiquette, handoff and cleanup. Use when you start, wait on, answer, or recover workers in Pane, from a Pane Session o...Votes: 0GitHub stars: 661
- Wrap UpWrap up a Pane Session in one step - take stock of its Panes, tell the person first about anything that needs their attention, archive every Pane that is safe to archive, close the tabs you opened, and report what was kept and why. The Session itself stays open; archiving it is the person's call. Use only as a Pane Session orchestrator, when the person types /wrap-up or asks to wrap up the Session.Votes: 0GitHub stars: 661
- PaneUse whenever you work with Pane (the desktop app that runs coding agents in parallel git worktrees) through runpane or the pane MCP: in a Pane terminal (PANE_SESSION_ID is set), for Panes, panels, Sessions, agent tabs, asking the person (notify), showing a page, reading or sending to another panel, reaching another machine, or when runpane or the pane tools seem missing.Votes: 0GitHub stars: 661
- Planner ProofReport the unique Orchestra test marker when explicitly requested.Votes: 0GitHub stars: 9
- Worker ProofReport the unique Orchestra test marker when explicitly requested.Votes: 0GitHub stars: 9
- Astra TicketTake a work item through Astra planning, Sol implementation, concurrent checks and focused reviews, optional Sol QA, and a final current-head PR review.Votes: 0GitHub stars: 9
- AuditsAudit stale GitHub issues, stale open PRs, and stale agent-facing docs (AGENTS.md, CLAUDE.md, generated contracts, CI/toolchain copy, README examples) against the default branch. Use when the user asks to close stale issues, sweep the backlog, check whether AGENTS.md or docs are outdated, or run repo hygiene on issues, PRs, and documentation.Votes: 0GitHub stars: 9
- Babysit PrUse after a pull request is open to watch its CI and review-bot comments until it is ready. Fixes real findings, replies with a reason to false positives, rebases when the base moves, and stops when bots and required checks are green. Merges only when the person asked.Votes: 0GitHub stars: 9
- Business Agent SkillsCoordinate a business deliverable from context and discussion through specification, drafting, review, and release preparation.Votes: 0GitHub stars: 9
- Business ArtifactDraft and review a business deliverable from an approved specification.Votes: 0GitHub stars: 9
- Business DiscussionClarify a business deliverable's goal, audience, and decisions from gathered context before drafting.Votes: 0GitHub stars: 9
- Business Prepare ReleasePrepare a reviewed business artifact for release, delivery, or human approval.Votes: 0GitHub stars: 9
- Business SpecTurn a business discussion brief and sourced context into a reviewed deliverable specification.Votes: 0GitHub stars: 9
- Create PlanCreates a reconciled implementation plan by combining a structured plan draft with a normalized intent brief and a PRP-style research dossier, then auto-reviews the final plan. Use when planning a new feature or significant change in Codex.Votes: 0GitHub stars: 9
- Deep Dive RefreshRevisit a previous deep dive, research brief, or Grain with fresh evidence and first-principles reasoning; identify what changed, what still holds, and what the earlier investigation missed, then update the existing artifact. Use for a fresh check, research refresh, or reassessment of prior findings.Votes: 0GitHub stars: 9
- Deep DiveInvestigate a topic, market, organization, practice, trend, or decision across primary sources, communities, directories, reviews, and structured web data; produce a clear, cited synthesis with evidence gaps and practical implications. Use for substantial deep research or expanding an existing research brief, not a simple factual lookup.Votes: 0GitHub stars: 9
- Excalidraw Pr DiagramsCreate Excalidraw diagram JSON files and PR visual overviews that make visual arguments. Use when the user wants to visualize workflows, architectures, concepts, pull request changes, before/after behavior, or a shareable explainer image for reviewers.Votes: 0GitHub stars: 9
- Explain VisuallyComplement an answer or discussion with a first-principles visual HTML explanation, saved in Grain when connected. Use when explaining how something works, why it changes, or how options differ and a visual would materially help understanding, including requests like "show me" or "help me understand." Skip simple factual answers and text-only requests.Votes: 0GitHub stars: 9