All authors
Claude Skills by arcasilesgroup
github.com/arcasilesgroup42 skills0 installs20 views
- Ai DebugFinds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves merge and rebase conflicts by intent rather than by taking a side. Trigger for "it's not working", "this used to work", "I'm getting an error", "CI is failing", "why is X happening", "I have conflicts", "the rebase failed". Not for adding test coverage to working code — use /ai-verify. Not for exploring an unfamiliar area — use /ai-explor...Votes: 0GitHub stars: 60
- Ai ExploreAnswers questions about this repository by reading it, anchored to file:line, and tours an unfamiliar area for somebody who has just arrived. Trigger for "where does X live", "how does this work", "why does it do that", "what depends on Y", "walk me through", "map this module", "trace this import chain", "onboard me". Not for evidence from outside this repository — use /ai-research. Not for diagnosing a failure — use /ai-debug. Not for judging a diff — use /ai-verify.Votes: 0GitHub stars: 60
- Ai NoteSaves a finding that took real time to reach — a non-obvious behaviour, an integration trap, a workaround and the reason it is needed — as committed markdown, stamped with the commit and the file patterns it describes so that it can be detected as stale later. Searches those notes too. Trigger for "save this", "note that", "remember this", "we worked this out the hard way", "do we have notes on", "what did we find about". Not for project decisions — use /ai-brainstorm, which is where a decisi...Votes: 0GitHub stars: 60
- Ai ResearchFinds evidence from outside this repository and reports it with numbered citations, or marks a claim [unsourced] and leaves it marked. Uses only the tools the client actually has: the local floor is always on, web search / Tavily / Exa run only when the client configured them, and NotebookLM deep research runs only when `notebooklm doctor` passes — an absent tool degrades and is named, never an error. Ends with three cited directions worth taking. Trigger for "what does the state of the art s...Votes: 0GitHub stars: 60
- Ai SecuritySix-phase security audit of a codebase — web apps, APIs, services, CLI tools, libraries, and daemons — with adversarial validation: the agent that verifies a finding is never the one that found it. Recon, parallel hunting across 8 attack classes, validation, reporting, schema-validated findings.json, and independent verification. Only exploitable issues with real impact are reported — never theoretical concerns or industry-standard behavior. Use when a milestone declares a security audit, whe...Votes: 0GitHub stars: 60
- Ai VerifyUse when work has to be verified — "verify the feature", "did we build what was asked", "review this diff", "is it ready to commit" — by choosing the right verification tier (standalone, embedded, or chain) and producing verdicts with evidence, not impressions. Not for milestone-declared security audits — use /ai-security. Not for diagnosing a failure — use /ai-debug.Votes: 0GitHub stars: 60
- Ai Visual RecapTurn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes. Trigger for "recap this PR", "summarize the change for review", "show me what this branch changed". In ai-engineering it runs when CLOSING a milestone (step 12), not on demand; the artifact lives at .ai-engineering/recap.html. Not for judging whether the work is any good — use /ai-verify.Votes: 0GitHub stars: 60
- Ai WriteWrites technical documentation for this repository: a README, a wiki page, product documentation, API docs or a technical post. Applies the framework's single writing standard (`references/documentation-writer.md`) and verifies every document against the tree. Trigger for \"write the README\", \"update the wiki\", \"document this API\", \"write a technical post about\", \"refresh the docs\". Not for the changelog. Not for a feature plan — use /ai-orchestrator. Not for a finding — use /ai-note...Votes: 0GitHub stars: 60
- Ai Agents MdCreates, audits and maintains the AGENTS.md a repository owes its coding agents, following the agents.md convention (https://agents.md/). Decides root-only versus nested AGENTS.md files from the repo's real shape, interviews the tree (not the user) for build/test/lint commands, and writes only what an agent cannot deduce from the code. Audits a set that already exists: a rule the code states, a child repeating its parent, a command that no longer runs, a zone with no route in. Also the in-ses...Votes: 0GitHub stars: 60
- Ai ArchitectResearch and advise on the best way to approach a software project, including architecture, tech stack, implementation strategy, pricing/operating-cost tradeoffs, benchmark research, and comparisons with similar real-world projects. When the project hinges on a technical mechanism, it can also run a gated arXiv prior-art deep dive before recommending a path. Use before building, mid-build, or after completion when the user asks for project strategy, optimal approach, research comparables, sim...Votes: 0GitHub stars: 60
- Ai BrainstormUse when the user brings a fuzzy idea that must be pinned down before research or planning — "handshake", "get on the same page", "align on this idea", "let me explain my vision", or before ANY creative work (a feature, a component, a behavior change). One question at a time until the whole idea can be explained in 3rd-grader language, the request classified (spike / bounded / architectural), the design approved, and the result captured in a self-contained doc that a researcher agent and a pl...Votes: 0GitHub stars: 60
- Ai Issue ReportReports a reproducible fault to a team or an upstream project — for ai-engineering itself or for any service the client is building — as a governed payload: closed allow-listed fields, scanned for machine paths, personal data (PII) and secrets before anything is written, draft kept local, and the exact bytes shown with their SHA-256 before anybody confirms anything. Trigger for "report this bug", "file an issue", "the framework is broken", "send this upstream", "write the incident report". No...Votes: 0GitHub stars: 60
- Ai Read DocsUse when the work depends on versioned or external behaviour — adding a package, writing setup or config, integrating an SDK or a paid API, debugging a framework change — or on anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, co...Votes: 0GitHub stars: 60
- Ai Stress TestTest system behavior under extreme load to find breaking points, capacity limits, and failure modes. Covers stress, spike, and breakpoint testing with k6 (primary), JMeter, or Locust. Refuses unbounded concurrency and production saturation without explicit approval. Trigger for "stress test", "load test until it breaks", "find the breaking point", "capacity test", "spike test", "how much traffic can we handle", "system limits", "what's our max load". Not for frontend performance or Core Web V...Votes: 0GitHub stars: 60
- Spec ExtractTurn an unwritten agreement into a checkable spec — pull the requirements out of this conversation, a ticket, a pasted thread, or a design discussion, and write them to the project's spec file as numbered, falsifiable claims. Use before starting a feature, when the user says "write this up", "turn this into a spec", "make a design doc", "what did we agree", "capture the requirements", or "create design.md"; when a review skill halts because no spec exists; and at the point a conversation has ...Votes: 0GitHub stars: 60
- Verify FeatureVerify that a feature as built actually matches what was asked for — catching requirements that were quietly dropped, built differently than specified, or built without being asked for. Use this whenever you are partway through or wrapping up a feature and about to call it done, and whenever the user says "does this match the PRD/spec", "did we drift", "is this what I asked for", "check this against the requirements", "verify the feature", "did you build everything", or reviews work before a ...Votes: 0GitHub stars: 60
- Feature VerifyCross-verify a just-finished feature with throwaway browser tests driven by chrome-headless-shell — proves the feature actually does what it was supposed to do, and proves the change didn't break the routes and components that depend on it. Reports a verdict with evidence and never edits app code. Use this whenever a feature, fix, refactor, or UI change has just been completed — including when the user says "done", "that's implemented", "verify this", "does it work?", "make sure nothing broke...Votes: 0GitHub stars: 60
- Second OpinionGet an independent review of code you just wrote by spawning a fresh reviewer instance — a separate one-shot agent session with read-only tools that cannot see your reasoning. Use this immediately after finishing ANY implementation — a feature, a bugfix, a refactor, a migration, a schema change — before you tell the user the work is done. Also use whenever the user says "review this", "double-check that", "get a second opinion", "have another agent look at it", or asks whether an implementati...Votes: 0GitHub stars: 60
- A11y AuditAudit the UI for accessibility defects against WCAG 2.2 AA — semantic structure, keyboard operability, focus management, form labeling, ARIA correctness, contrast, and motion — with each finding tied to the user it locks out. Use when asked to check accessibility or a11y, review UI for screen-reader or keyboard support, or verify WCAG compliance.Votes: 0GitHub stars: 60
- Build CheckRun the project's objective quality gates — typecheck, lint, tests, and a production build, whatever this project actually uses — then diagnose any failure down to the file and root cause. Use before committing, opening a PR, or declaring work done, and whenever asked whether the code compiles, typechecks, lints, tests, or builds.Votes: 0GitHub stars: 60
- Code AuditReview code for correctness bugs, concurrency and lifecycle errors, type-safety holes, error handling gaps, API-contract breaks, and maintainability problems, with every finding gated on a concrete failure scenario. Use when asked to review code, check a diff or branch for bugs, look for problems before committing or opening a PR, or assess code quality.Votes: 0GitHub stars: 60
- Design CheckVerify the implementation actually matches design.md — builds a requirement-by-requirement traceability table showing what is implemented, partial, missing, or contradicted, plus undocumented behavior the code added on its own. Use when asked to check code against the design/spec, confirm a feature was built as designed, find drift between design.md and the app, or answer "did we build what we said we would".Votes: 0GitHub stars: 60
- Full ReviewRun every review skill at once — build-check, then design-check, code-audit, security-audit, a11y-audit and perf-audit fanned out across parallel agents — and merge them into one deduplicated, severity-ranked report. Use when asked for a full/complete review, to review everything before shipping or merging, or to run all the checks.Votes: 0GitHub stars: 60
- Perf AuditAudit performance — payload and bundle size, data-access patterns and waterfalls, caching, assets, and compute cost — reporting only issues with a measurable, user-visible cost. Use when asked about performance, slow loads, slow queries, slow renders, bundle size, memory use, Core Web Vitals, or optimizing the app.Votes: 0GitHub stars: 60
- Review RouterDecide which review lanes a change actually needs, then run exactly those — instead of spawning the whole chain at every diff size. Reads the diff's shape and blast radius, maps the evidence to lanes (code, security, a11y, perf, design, build), estimates the cost, shows the routing decision, and executes it. Use when asked to "review this", "check this before I commit/merge", "is this ready", or "what should I run", and whenever a full review would cost more than the change is worth. Prefer t...Votes: 0GitHub stars: 60
- Security AuditAudit the codebase for exploitable security issues — traces attacker-controlled input to dangerous sinks across HTTP handlers, background jobs, auth and access control, and anything shipped to the client, and checks dependencies for known CVEs. Use when asked for a security review or audit, to check for vulnerabilities or leaked secrets, or before shipping code that handles auth, user input, or external requests.Votes: 0GitHub stars: 60
- Ai Writing BehaviorAuthors and revises Agent Behavior BEHAVIOR.md specs that capture recurring, judgeable agent conduct. Use when creating, reviewing, splitting, grouping, or calibrating behavior specs, or when translating trace failures and runtime guidance into durable behaviors. Trigger for "write a behavior spec", "turn this failure into a behavior", "calibrate this behavior", "BEHAVIOR.md". Not for merely scoring a completed trajectory — use /ai-verify — nor for writing a runtime prompt.Votes: 0GitHub stars: 60
- Ai Adversarial LoopCoordinate a multi-round debate between two agents until the code is clean. adversarial-reviewer (the critic) assumes everything is wrong; fixer implements fixes or disputes them with evidence. They exchange findings through a shared thread file, and each keeps its memory across rounds. Use as the orchestrator's review gate, or when the user asks for an adversarial review-and-fix loop on recent changes (e.g. "/ai-adversarial-loop", "have the critic and fixer go at checkpoint 3").Votes: 0GitHub stars: 60
- Ai Audit CodeForces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Al...Votes: 0GitHub stars: 60
- Ai Audit DesignUse when a web interface needs its visual defects found and fixed with measurements rather than opinions — misaligned rows, ragged card interiors, touch targets, rendered contrast over gradients and images, text printing over text, Gestalt proximity, divider lines that should be space, and type-scale drift — measured in a real browser across widths, and proved unchanged afterwards. Not for electing a lead or sequencing design work — use /ai-design.Votes: 0GitHub stars: 60
- Ai Audit DocsAudits documentation files against actual repo state. Detects dead references (links to nonexistent files/URLs), false claims (doc says feature X exists but the code doesn't), outdated version numbers, and references to commands that don't exist. Input: path to docs dir or specific files (defaults to docs/ README.md AGENTS.md). Output: ranked markdown table of findings with severity and location. Report-only, NO auto-fix. Trigger phrases: "audit docs", "check documentation", "verify docs", "d...Votes: 0GitHub stars: 60
- Ai Code ReviewComprehensive code review skill. Two modes: diff review for over-engineering findings (ranked, compact), and debt collection for deferred shortcut ledgers. Checks against AGENTS.md code style rules (KISS, YAGNI, DRY, early returns, naming). Use when the user asks to "review code", "code review", "find over-engineering", "check for bloat", or "review this diff". Not for diagnosing runtime failures — use /ai-debug. Not for judging correctness of a diff — use /ai-verify. Not for writing document...Votes: 0GitHub stars: 60
- Ai CodegraphSemantic code intelligence via MCP: call chains, blast radius, cross-file symbol relationships. Uses CodeGraph (colbymchenry/codegraph) — a local-first Rust server that builds a SQLite knowledge graph from tree-sitter ASTs. One tool: codegraph_explore. Use when the question involves "how does X work", "what calls Y", "if I change X what breaks", or cross-file dependency analysis. Not for literal text search — use find/grep for that. Not for file discovery — use glob. Trigger for "codegraph", ...Votes: 0GitHub stars: 60
- Ai Config To ProjectAdapts a governed project's architecture rules, config, overrides, and AGENTS.md after ai-eng init. Manual only. Writes a proposal page and stops until the person says yes, then runs ai-eng adapt apply. Trigger for "/ai-config-to-project", "adapt this project", "the init rules are wrong for this repo".Votes: 0GitHub stars: 60
- Ai Design Md PlannerInterviews the user about their product and visual taste, commits to a specific referenced aesthetic direction, and writes a DESIGN.md design system file in Google's DESIGN.md format — then audits it with the official `@google/design.md` CLI until it lints clean. Use this skill whenever the user wants a design system, design tokens, a DESIGN.md, a style guide, a brand/visual identity, a color palette or type scale for a product, wants to "make this look good" or "not look AI-generated," wants...Votes: 0GitHub stars: 60
- Ai OrchestratorBuild a whole feature end-to-end through subagents. It plans gated checkpoints, writes tests and prototypes, then loops each checkpoint through implement → behavior gate (CLI/code tests, UI e2e last) → UI gate (live vs prototype) → adversarial review gate until every checkpoint passes, then hands it to a human to review. Use when the user says "build X", "orchestrate X", "/ai-orchestrator <feature>", or asks to resume an orchestrated feature.Votes: 0GitHub stars: 60
- Ai PrototypeBuild a single-file, clickable HTML prototype of a UI screen or flow, following the design directions given in the request. Use when the user asks to prototype, mock up, or sketch a UI (e.g. "/ai-prototype order list, dense, neutral palette", "mock up the settings page").Votes: 0GitHub stars: 60
- Ai Review UiCompare the live UI of the web app against its HTML prototype in .ai-engineering/workflow/prototypes/ and report the visual and behavioral gaps. Screenshots both, then two parallel reviewers (subagents, or `claude -p`) diff them, one for visuals and one for behavior. Use when the user asks to review, check, or diff the implemented UI against a prototype (e.g. "/ai-review-ui order-list", "does the settings page match the prototype?").Votes: 0GitHub stars: 60
- Ai Test PlannerPlan and write the tests for a feature, bottom-up. Everything that code or the CLI can verify (pure logic, API endpoints, DB constraints, auth/role rules) is tested without a browser. UI end-to-end tests come last and cover only what the lower layers can't. Use when the user asks to plan tests, write tests, or add test coverage for a feature or checkpoint (e.g. "/ai-test-planner discount rules").Votes: 0GitHub stars: 60
- Ai Git CleanupRemoves finished local git work in one automatic pass, with no question and no name to type: dead worktrees first (`git worktree remove`, then `git worktree prune`), then branches already merged into the local `main`, then the branches a squash-merged pull request left behind (tree identical to `origin/main`, tagged before deletion). Trigger for "tidy up", "tidy up these branches", "tidy branches", "delete old branches", "start fresh", "limpieza de branches", "limpia branches", or by naming a...Votes: 0GitHub stars: 60
- Ai Github TriageReads every open issue and pull request of a repository and writes one ranked, actionable page at .ai-engineering/triage.html: what is broken, what is already answered, what to close, and the three things to start on first, each claim backed by a permalink at a commit SHA. Read-only: it never comments, labels, closes, merges or reviews anything on GitHub. With no argument it triages this repository; given a URL or owner/repo it triages that backlog instead. Trigger for "triage", "triage the i...Votes: 0GitHub stars: 60
- Ai PrThe pull-request loop, opened from the local `main` with no worktree: cut the pull-request branch from the local `main`, push it, open the pull request against `main` with a body assembled from the merge commits the branch carries, watch CI and the review comments, fix only what is obvious in bounded iterations, then merge with auto-merge on by default. The human's verb decides how far the run goes: "open the pull request" opens it and stops, while "finish the PR", "land the PR", "merge it" o...Votes: 0GitHub stars: 60