All authors
Claude Skills by heyJordanParker
github.com/heyJordanParker114 skills9 installs209 views
- Agent BrowserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use...Votes: 0GitHub stars: 22
- ArchitectureTRIGGER when presenting Architectural options, Architecting systems, or discussing tradeoffs. Append to any Prompt.Votes: 0GitHub stars: 22
- CcWrite and fix Claude Code Prompts — skills, agents, commands, hooks, rules files, Claude.md, and plugin distribution. TRIGGER when the task says "cc"/"claude code"/"claude-code", or asks to build, edit, test, or share a skill/agent/hook/command, tune a description's triggering, write or prune a Claude.md, or cut prompt bloat. DO NOT TRIGGER to name a Claude.md's identifiers (that is /naming) or to record domain vocabulary (that is /domain-design).Votes: 0GitHub stars: 22
- ReferencesThe Process for syncing /cc with a Claude Code release that changes how Agents write, load, test, or distribute Prompts.Votes: 0GitHub stars: 22
- Code FirstAutonomous async Execution. The Architect hands off and walks away; the Agent drives the Task to done — makes every Architectural call by tracing the code and finding every option with /discover, executes through /delegate, verifies from each implementing Subagent's Evidence (they exercise their own flows, real browser for UI), and returns finished code plus the recorded Decisions for review. TRIGGER when the Architect says "code-first", "/code-first", "execute with /delegate", "execute direc...Votes: 0GitHub stars: 22
- DebateRun N independent architect Agents debating Architectural options through rounds. TRIGGER when the Architect wants multiple competing Solutions evaluated, when 3+ distinct approaches need comparison, or when the Prompt says "debate", "competing solutions", "run architects", "architecture debate", or `/debate [count] "problem"`.Votes: 0GitHub stars: 22
- DebugUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 22
- DesignTRIGGER when building UI components, styling pages, or making visual/interaction Decisions. Guides design thinking, anti-patterns, CSS Architecture, and responsive patterns.Votes: 0GitHub stars: 22
- DiagramGenerate Excalidraw diagrams with a hand-drawn aesthetic. Pushes elements to a live Excalidraw canvas via HTTP API, or renders to PNG/SVG.Votes: 0GitHub stars: 22
- Gh IssueCreate or update GitHub issues. Writes the durable context an Agent cannot rediscover — the Problem, the WHY, the systems it crosses, the impact — and leaves the tactical HOW to the Agent that picks it up. Use when the Architect says "create an issue", "file an issue", "gh issue", "update the issue", or wants to turn a Plan into a trackable issue.Votes: 0GitHub stars: 22
- Independent ReviewRun N identical parallel Subagents on the same Task for independent Verification. Use when the Architect wants consensus through redundancy — multiple Subagents independently analyze, review, or test the same thing, then the combined returns are triaged with /triage. Invocation /independent-review [count] "task"Votes: 0GitHub stars: 22
- ModelingTransform Shaping output into a concrete Modeling artifact — database schema, User experience, and Architecture. TRIGGER between Shaping and Slicing, or when the Architect asks to model an existing system before Execution.Votes: 0GitHub stars: 22
- NamingMANDATORY for naming any code identifier — variable, function, file, folder, class, database column, route, CSS class. Always returns a 5-10 candidate slate; the caller picks. TRIGGER when proposing or choosing a name, on /naming, on "rename", "ideas", "options", "what should I call", or any new file/class/method/column/route. DO NOT TRIGGER when editing a body that does not introduce or change an identifier, when restructuring code (Architecture, not naming), or when labeling UI for end Users.Votes: 0GitHub stars: 22
- Pragmatic EngineeringKeep engineering boring and complete. TRIGGER when the Architect says KISS, pragmatic, don't overengineer, ship it, keep it simple, or asks for a pragmatic read on a Proposal, Plan, code review, or Architectural Decision. DO NOT TRIGGER when the Architect asks for maximum rigor over shipping pressure.Votes: 0GitHub stars: 22
- RegressionsCheck a diff for Capability regressions — loss of User-facing Capability ("the User can no longer X") or loss of system Capability ("our system can no longer Y"). Maps changed code to affected Critical Path and system Capabilities, traces each through the code, and reports any that no longer work. TRIGGER on "/regressions", "check for regressions", "regression review", or before merging changes that touch Critical Path or system functions.Votes: 0GitHub stars: 22
- ReviewRead the changeset yourself, review it with one Claude reviewer and one codex reviewer on the same target at once, triage their findings with /triage, and iterate until a round returns no breaking finding. TRIGGER on "review the changes", "code review", on the Review before a changeset is presented to the Architect, and when a /orchestrate or /verify-changes step names it. DO NOT TRIGGER for N identical reviewers on one Task (that is /independent-review).Votes: 0GitHub stars: 22
- ShapingCollaborative Shaping with the Architect: capture requirements, boundaries, shapes, fit checks, research unknown mechanics, and transition to Modeling then Slicing. TRIGGER when the Architect asks to shape, scope, compare approaches, or turn a rough idea into a modeled change.Votes: 0GitHub stars: 22
- SlicingTurns a shaped and modeled change into vertical Slices with acceptance criteria and Verification requirements. Each Slice ends in demo-able functionality. The Plan becomes an immutable contract.Votes: 0GitHub stars: 22
- TraceCode intelligence for the local codebase — search, callers, definitions, symbols, complexity, and file or method reads, each carrying the file's facts and the project docs not yet loaded. TRIGGER whenever you need to find, understand, or trace relationships in code instead of raw grep or unfiltered file reads.Votes: 0GitHub stars: 22
- User TestingTests code changes by tracing real Critical Paths. Lists Critical Paths affected by uncommitted changes, spawns one Subagent per Critical Path to trace Execution and find gaps, then evaluates Architecturally. TRIGGER when the Architect says "user test", "test the Critical Paths", or "trace Critical Paths".Votes: 0GitHub stars: 22
- BuildThe build mode's contract — the Agent does every edit and run itself, with no Subagents, deep full-file reads, and research before acting. TRIGGER when the session enters build mode, on the /build command, and when build mode is re-injected after compaction. DO NOT TRIGGER for orchestrate mode, where Subagents do the work (that is /orchestrate).Votes: 0GitHub stars: 22
- CodexDrive codex CLI runs as your Agents — you own Orchestration, codex does the work. One wrapper, `codex-run`, owns the mechanics (flags, output storage, stream parsing, failure detection); you write the Task Prompt and do the judgment. Calls /delegate for Orchestration doctrine on a codex-run substrate. TRIGGER when the Architect says "codex", "/codex", "codex-run", "use codex", "dispatch to codex", "run this through codex", "codex agents", "review with codex", "codex review", or asks to fan ou...Votes: 0GitHub stars: 22
- CommitMandatory contract for every commit. The classifier names it when it authorizes a commit — it injects "Skills to execute: /commit" whenever the Architect asks to commit ("/commit", "commit this", "create a commit"). Holds the whole commit job: commit your own changes, write the message, commit, verify, then suggest which session notes should become permanent — plus the commit-message format (type prefix, Capability subject, Problem and Solution body, file tree). TRIGGER on every commit-author...Votes: 0GitHub stars: 22
- Critical PathProcess for changes with a large blast radius — files with many callers or repo-p95 complexity, and actions that are destructive, hard to reverse, or visible outside the repo. TRIGGER before editing a file whose enrichment context shows callers ≥ 20 or complexity at the repo p95, and before any delete, force-push, schema drop, process kill, push, pull-request operation, shared-infrastructure change, or third-party upload.Votes: 0GitHub stars: 22
- DelegateFramework for dispatching one-shot Subagents that complete a Task and return. Covers Prompting (WHY -> WHAT -> HOW), the Story/Business/Goal/Verification/Process Prompt Template, and Evidence directories. TRIGGER when dispatching or resuming Subagents, when Orchestration needs the dispatch Prompt Template, or when the Architect says "/delegate this to ...". DO NOT TRIGGER for judging what a Subagent returned (that is /orchestrate), or for work the Agent does itself with no Subagents; use /build.Votes: 0GitHub stars: 22
- Domain DesignBuild or sharpen a project's Domain.md and Decisions. Use when the Architect wants to pin down project language, record a Decision, or when another Skill needs to change Domain.md.Votes: 0GitHub stars: 22
- ExecuteMandatory contract for every executing-state turn. The classifier names it when the Architect types /execute, and every 30 turns after that while the session is executing. Implements the work the Architect approved; when that work needs an Architectural change, stop and escalate instead of deciding. TRIGGER on every executing-state turn — the classifier mandates this. DO NOT TRIGGER for proposing turns (that is /propose) or auto turns.Votes: 0GitHub stars: 22
- HandoffCompact the current conversation into a handoff document for another Agent to pick up.Votes: 0GitHub stars: 22
- ImpeccableUse when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing,...Votes: 0GitHub stars: 22
- InterviewInterview the Architect to plan complex Architectural work before any code is written. Use when the Architect asks for an interview, or a Plan or Proposal needs his Decisions before Execution.Votes: 0GitHub stars: 22
- MergeAn Agent merges two branches one file at a time and checks each file against its two parents, so both sides' code survives while one side's feature stops working and no file-level check sees it. This Skill merges the branches and proves every behaviour each side committed still runs afterward. TRIGGER when merging two branches that both carry behaviour-changing commits since the merge base, on "/merge", "audit the merge", and whenever a behaviour is missing from a tree that was already merged...Votes: 0GitHub stars: 22
- OrchestrateThe orchestrate mode's contract. You own the Architecture and spend your whole capacity on it — Subagents make every change, and you validate what they return with read-only checks. TRIGGER when the session enters orchestrate mode, on the /orchestrate command, and when orchestrate mode is re-injected after compaction. DO NOT TRIGGER for build mode, where the Agent does the work itself with no Subagents (that is /build).Votes: 0GitHub stars: 22
- PresentPresent information to the Architect so he can act on it. TRIGGER on every reply that carries a Decision, a finding, or an Architectural discussion, and on /present. DO NOT TRIGGER for drawing one diagram; that is /show-me.Votes: 0GitHub stars: 22
- Progressive ResearchBroad-to-narrow research Orchestration - start with a wide census, harden the scope from returned Evidence, and specialize Subagents only once the exact situation is proven. TRIGGER when the Architect says "progressive research", "start broad", or when dispatching research or debugging Subagents into a situation whose cause or shape is unknown. DO NOT TRIGGER when the exact scope is already proven - use /delegate to dispatch the specialized Subagent directly.Votes: 0GitHub stars: 22
- ProposeMandatory contract for every proposing-state turn. The classifier names it when the Architect types /propose. Routes every decision to its layer, researches until the Proposal names files, methods, and data changes, orders the Decisions by dependency, shows each one with its code and options, and fixes the findable flaws before sending. TRIGGER on every proposing-state turn — the classifier mandates this. DO NOT TRIGGER for executing turns (that is /execute) or auto turns (mixed intents resol...Votes: 0GitHub stars: 22
- ProveProduce the Evidence that proves work is done before any completion claim.Votes: 0GitHub stars: 22
- ResearchSource-grounded external research for current library, API, framework, service, and vendor behavior. TRIGGER when the Task asks for current facts, docs, releases, compatibility, adoption, or external technical Decisions. DO NOT TRIGGER for in-codebase Architecture tracing; use /trace or the explorer agent.Votes: 0GitHub stars: 22
- Show Me HtmlBuild and publish the page the Architect reviews an Architecture Proposal on — one self-contained page toggling between the start state and the final state across architecture diagrams, annotated file trees, and database changes. TRIGGER when the Architect fires this Command by name. DO NOT TRIGGER to show Architecture inline in a reply (use /show-me) or to review code changes (use /review).Votes: 0GitHub stars: 22
- Show MeDraw every code change in the reply as a diff, an annotated file tree, or a class diagram, and keep ideas in prose. TRIGGER on every reply that explains code, Architecture, a change, a name, or a finding, and whenever the Architect says "show me". DO NOT TRIGGER to score a set of options; that is /rank.Votes: 0GitHub stars: 22
- TriageTurn returned reviewer findings into one graded report grouped by who each problem affects, and act on the gate. TRIGGER after review Subagents return findings — from /review, /regressions, /user-testing, or any audit — and before results reach the Architect. DO NOT TRIGGER while reviewers are still running, or for a single finding routed directly to its owner.Votes: 0GitHub stars: 22
- UnderstandDeep research of the systems behind a change — name the systems, show the architecture, read the git history for intent, trace the code, attack the understanding, and report in a layered file another Agent can act on coherently. TRIGGER when a change lands in a system the Agent has not mapped, when the Architect says "understand the system first", "research the architecture", "deep research", or "how did this come to be", and when a dispatch brief asks for system research. DO NOT TRIGGER for ...Votes: 0GitHub stars: 22
- Verify ChangesVerify the whole changeset the way the User meets it: the suite, the Review gate, the Critical Paths, once every Task has landed. TRIGGER when the last Slice is staged, when an autonomous run reaches functional completion, or on "verify the changes". DO NOT TRIGGER with Tasks still open, where the Orchestrator judges each Task's returned Evidence instead.Votes: 0GitHub stars: 22
- Analyze VoiceBuilds a Voice.md profile from a writer's existing samples — reverse-engineers the patterns that make their copy sound like them, then writes a structured, reusable profile the rest of the team applies at write time. TRIGGER when asked to capture, define, or learn a voice, build or regenerate a Voice.md, analyze writing samples for tone, or set up a new product's voice. DO NOT TRIGGER when writing or editing copy against an existing Voice.md — writing copy is the copywriting skill, matching i...Votes: 0GitHub stars: 22
- Big IdeaFind the BIG IDEA of a piece — the one fresh, charged idea the whole thing hangs on, spiky enough that the reader stops and feels it. TRIGGER when a piece needs its core idea found or sharpened, when a draft reads as flat or generic, or when a headline or angle has no single idea underneath it. DO NOT TRIGGER for line polish (edit-sentences) or for writing the body once the idea is set (copywriting).Votes: 0GitHub stars: 22
- BrowseRead one web page for research — a plain-HTTP fetch that passes bot walls headless browsers cannot, cleaned to its main content, cached, and recorded in the source registry. TRIGGER when a research or review step needs a page's text. DO NOT TRIGGER to screenshot a page or drive an interactive surface (screenshot, agent-browser), or to score a source you have already read (review-source).Votes: 0GitHub stars: 22
- Buyer ReviewRead the piece AS the product's owner-approved buyer — believable, valuable, would they pay. Belief lives here. TRIGGER when a draft needs the buyer's reaction, a believability read, or when the Buyer Reviewer loads it for the review-as-a-buyer stage. DO NOT TRIGGER for whether a claim is technically backed (check-claims), the CTA path (cro-review), or line quality (edit-sentences).Votes: 0GitHub stars: 22
- Check Ai WritingThe sole de-slop pass — AI tells, metaphors and metaphorical verbs, synthetic cadence, template smell, and the additive distinctiveness check. Anything whose cause is genericness. TRIGGER when de-slopping a draft, hunting AI tells or generic SaaS phrasing, or when the editor loads it for the check-for-ai-writing stage. DO NOT TRIGGER for within-sentence clarity or economy (edit-sentences), section joins (check-structure), or claim backing (check-claims).Votes: 0GitHub stars: 22
- Check ClaimsTrace every claim in a piece to a research record or a product fact — proof presence lives here. Unsourced claims are listed, never shipped, never auto-killed; they escalate to the chief. TRIGGER when fact-checking a draft, verifying claims and proof, or when the Fact Checker loads it for the check-the-claims stage. DO NOT TRIGGER for whether the reader believes the claim (buyer-review), for the CTA path (cro-review), or for genericness (check-ai-writing).Votes: 0GitHub stars: 22
- Check RealityAttack whether the market, buyer, problem, and language a research or strategy artifact claims actually EXIST — the reality-attack pass. Not improvement, destruction of fabricated reality. Every item gets a 1-to-100 existence-confidence rating with reasoning, default low; internal coherence is not evidence. TRIGGER on research records, a judged root file, a project's re-derived buyers or problems, an assembled strategy, or a built piece, or when the Reality Reviewer runs the reality attack. D...Votes: 0GitHub stars: 22
- Check StrategyJudge whether the piece's argument holds — right buyer at the right awareness and sophistication, sections answering the buyer's real questions in a real order, and nothing starring that shouldn't lead. A strategic judgment gate argued from the buyer's perspective, not a checklist. Findings block. TRIGGER on the assembled selection at the assembly step (plan-copy 1d) before any plan file is written, and again on the built piece in the final pass, or when the chief runs the strategy gate. DO N...Votes: 0GitHub stars: 22