all publishers

ryanthedev

@ryanthedev source repo

46 published skills

  1. ▌
    Clarify 3 · ryanthedev
    Decomposes user intent through structured brainstorming before acting on ambiguous or underspecified requests — classifies the ambiguity type, generates competing interpretations, and selects the clarifying question that removes the most uncertainty. Use when requirements are unclear, a request could have multiple valid interpretations, critical details or constraints are missing, or the request contains contradictions. Most requests need no clarification — invoke only when a concrete ambiguity would change the approach. Not for: mechanical or well-specified tasks (renames, typo fixes, version bumps, running tests or commands, any edit with an explicit file and target), details you can determine yourself from the codebase, or full research or planning workflows that own their own scoping.
    387 repo stars
  2. ▌
    Clarify 2 · ryanthedev bundle
    Decomposes underspecified design requests by classifying gaps (missing brand context, visual ambiguity, false premises, scope faults) and generating targeted clarifying questions. Produces a confirmed design brief before any design work begins. For sharpening a design request that already exists; not for open-ended design brief discovery from a vague idea (use /design-for-ai:research).
    387 repo stars
  3. ▌
    Build Doctrine 4 · ryanthedev
    Implements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: for each Done-When item, write a failing test first, then the minimum code to make it pass (red-green).
    387 repo stars
  4. ▌
    Build Doctrine 2 · ryanthedev
    Implements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: stub the interface, implement it, then write tests that validate the Done-When items and any important behavior beyond them.
    387 repo stars
  5. ▌
    Build Doctrine 3 · ryanthedev
    Implements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: write failing tests first then code to pass (red-green), covering the Done-When items and important behavior beyond them.
    387 repo stars
  6. ▌
    Data Viz · ryanthedev bundle
    Applies data visualization and information design principles to encode data truthfully and efficiently. Use when the question is about charts or graphs — chart type selection (bar, line, scatter, heatmap, small multiples), data-ink ratio and chartjunk reduction (Tufte VDQI), preattentive attributes (Knaflic Storytelling with Data), dashboard layout and KPI design (Few Information Dashboard Design), truthful encoding and chart lie detection (Cairo How Charts Lie), marks and channels (Munzner), colorblind-safe palette selection for charts, or chart accessibility. Not for: brand or UI color palette generation (use core color mode); overall page composition and visual hierarchy (use core audit mode); data-display tables as a UI pattern (use usability); typeface or font selection (use core fonts mode); UI copy or writing (use content-design).
    387 repo stars
  7. ▌
    Prototype · ryanthedev bundle
    Produces self-contained HTML/CSS mockups and wireframes from design tokens and page specs — the output is always a viewable .html file, not guidance or code. Use when the request is to see a design, make a mock, build or show a prototype, create a wireframe, render a preview, or visualize what a page looks like before writing production code. Reads DESIGN.md tokens and JOURNEY.md page specs when present; uses greyscale wireframe defaults when absent. Renders via the browser MCP and returns a screenshot path when connected; emits the .html with an open note when not. Not for: choosing or defining fonts, colors, visual identity, or design tokens (use core design); critiquing, auditing, or reviewing an existing design (use core audit); planning IA, flows, or page specs (use journey); building a design token system or component library (use design-systems).
    387 repo stars
  8. ▌
    Usability · ryanthedev bundle
    Adjudicate whether users can operate an interface, and run heuristic evaluation. Use when the question is operability rather than looks — is it usable, hard to use, confusing, where do users get stuck; heuristic evaluation, Nielsen heuristics, usability audit, severity rating; the UX laws (Fitts, Hick, Miller/Cowan, Jakob, Tesler, Doherty, peak-end, Zeigarnik, aesthetic-usability); Gestalt grouping, affordances, signifiers, mapping, feedback, cognitive load, recognition over recall; picking among navigation, form, search/filter, table/data, feedback, action, disclosure, or onboarding patterns; or usability-side accessibility (WCAG POUR, inclusive design). Not for: the visual look or aesthetic audit (use core design/audit); the words/microcopy themselves (use content-design); the route through time, IA, or funnel (use journey); persuasion or conversion mechanics (use behavioral); truthful chart/data encoding (use data-viz).
    387 repo stars
  9. ▌
    Shot · ryanthedev bundle
    Captures and summarizes screenshots from the local desktop or a named window using the bundled capture script. Use when the user asks for a screenshot, screen capture, active-window capture, visual inspection of the current screen, or named-window screenshot. Not for browser-page screenshots when browser MCP tools are already controlling a page.
    387 repo stars
  10. ▌
    Agent · ryanthedev bundle
    Subagent dispatch guidance for the Agent tool — whether to delegate or work inline, the four-part delegation contract, model and effort selection, parallel fan-out sizing, fork vs fresh subagent, and dispatching independent verifier agents. Use before any Agent tool call: spawning subagents, fanning out work across files or research angles, delegating exploration or review, briefing a verifier, or deciding whether delegation is worth it at all. Not for: wording a prompt that isn't an agent dispatch (use oberskills:prompt) or authoring reusable skill and agent definition files — structure, frontmatter, and evals (use oberskills:skill-craft); their prompt bodies (use oberskills:prompt).
    387 repo stars
  11. ▌
    Write · ryanthedev bundle
    Drafts, edits, and reviews prose to remove the AI tells a model cannot see in its own writing — measured detection signals, not intuition: structural rhythm first (sentence-length variance, information density, discourse order), a reader-job type router second (narrative, expository, persuasive, marketing, expressive, announcement), the surface kill-list third (banned phrases, em-dash overuse, hollow openers, hedging), with optional private voice profiles and a phased interactive review for longer pieces. Use whenever prose for human readers is written, drafted, edited, or reviewed — blog posts, announcements, docs, emails, READMEs — when text needs humanizing, sounds robotic, or must match a specific person's voice. Not for: wording prompts or system-prompt text (use oberskills:prompt), converting markdown for platforms like Slack or Notion (use penman), or writing code, comments, docstrings, or API reference docs.
    387 repo stars
  12. ▌
    Prompt · ryanthedev bundle
    Design and review prompts Claude-first — system prompts, reusable agent definitions, long or novel dispatch briefs, pipeline stages, and prompts users will run elsewhere. Two modes: design and adversarial review. Covers Claude model behavior and migration, de-prompting, few-shot design, output-schema ordering, context engineering, prompt security, optimization, non-Claude/Codex target review via references/porting.md in this skill directory, and a verbatim behavior-snippet library. Use when writing, improving, debugging, reviewing, or migrating any prompt. Not for: creating, reviewing, or testing skill files (use skill-craft); routine subagent delegation prompts (use agent).
    387 repo stars
  13. ▌
    Browser · ryanthedev bundle
    Controls a live Chrome browser through a persistent puppeteer-core MCP connection — click, type, hover, drag, fill forms; navigate pages; take screenshots and export PDFs; read the DOM and accessibility tree; run Lighthouse audits and Core Web Vitals traces; intercept, record, stub, or block network requests; export HAR traffic; emulate devices and network conditions; manage browser storage; upload and download files. Use when interacting with or automating a running browser, clicking elements, taking screenshots, running Lighthouse, capturing network traffic as HAR, checking the accessibility tree, intercepting or stubbing requests, or emulating a device or viewport. Not for: web search or fetching public URLs without a browser session (use web-research), reading a static HTML file already on disk, fixing TypeScript or JavaScript build or compile errors, debugging source code without a running page, or tasks that don't require controlling a live browser.
    387 repo stars
  14. ▌
    Skill Craft · ryanthedev bundle
    Create, evaluate, and review Claude Code skills and reusable agent definition files (structure, frontmatter, evals). Covers the skill-vs-subagent-vs-hook decision, SKILL.md authoring and frontmatter, trigger-description optimization, baseline-first evals with pressure testing via the skill-eval MCP tools, validation, and packaging. Use when creating a new skill, improving or benchmarking an existing one, reviewing a skill directory, or writing evals for a skill. Not for prompt wording design or review — including the prompt body inside an agent definition (use oberskills:prompt), live subagent dispatch (use oberskills:agent), or prose editing (use oberskills:write).
    387 repo stars
  15. ▌
    Web Research · ryanthedev bundle
    Runs parallel multi-angle web research at four depth modes (scan, brief, breadth, deep): a planner grounds the query in local context and plans search dimensions, parallel search agents pull verbatim extracts with source URLs, one dimension always hunts counter-evidence, and synthesis is grounded back in the local project. Use when researching a topic, library, or tool on the web, comparing options or products, surveying a landscape of approaches, or checking current, version-sensitive, or time-sensitive information. Not for: driving or automating a live browser session (use oberskills:browser), academic literature search across arXiv or Semantic Scholar, or questions about the current repo, project, or files already on disk — read those directly.
    387 repo stars
  16. ▌
    Docs · ryanthedev bundle
    Search React Native official documentation. Use when answering questions about React Native APIs, components, hooks, layout, navigation, native modules, or platform-specific behavior. Triggers on "React Native", "RN docs", "how does View work", "FlatList props", "native module", "new architecture".
    387 repo stars
  17. ▌
    Clean · ryanthedev bundle
    Intelligent environment reset for React Native projects — diagnoses stale caches before cleaning instead of blindly nuking everything. Triggers on "clean build", "reset caches", "fresh start", "metro won't start", "build is broken", "nuclear clean", "clear derived data".
    387 repo stars
  18. ▌
    Debug · ryanthedev bundle
    Debug React Native apps — view console logs, JS errors, Metro status, evaluate expressions, inspect React component tree, monitor network requests. Use for runtime debugging of JavaScript and React layers. Triggers on "console logs", "JS errors", "Metro status", "evaluate expression", "React component tree", "network requests", "debug".
    387 repo stars
  19. ▌
    Coding · ryanthedev
    React Native coding guidance — consults official docs before writing code and suggests verification after. Use when writing components, implementing features, building screens, fixing queries, or adding views. Triggers on "write a component", "implement this feature", "build this screen", "add a view", "React Native code", "fix this query", "use best practices".
    387 repo stars
  20. ▌
    IOS Sim · ryanthedev bundle
    Control the iOS Simulator — tap, type, swipe, screenshot, record video, install and launch apps. Use when interacting with the iOS simulator during React Native development. Triggers on "simulator", "tap", "swipe", "screenshot of simulator", "install app", "launch app", "what's on screen", "record video", "accessibility tree", "tap by label", "tap by id", "list elements", "go back", "scroll to top", "scroll to bottom".
    387 repo stars
  21. ▌
    Diagnose · ryanthedev bundle
    Diagnose React Native errors by cross-referencing error text against docs, error pattern database, and project config. Use for build failures, red screens, runtime crashes, and dependency issues. Triggers on "diagnose this error", "why is my build failing", "what does this red screen mean", "Unable to resolve module", "null is not an object", "Invariant Violation", "pod install failed", "gradlew failed", "EACCES", "metro error".
    387 repo stars
  22. ▌
    A11Y Audit · ryanthedev bundle
    Audit accessibility of the running React Native app. Captures the accessibility tree from the iOS Simulator and checks it against React Native best practices. Triggers on "audit accessibility", "check a11y", "VoiceOver check", "accessibility issues", "screen reader test", "are labels correct".
    387 repo stars
  23. ▌
    Layout Check · ryanthedev
    Verify visual layout against React Native Flexbox and style documentation. Captures the simulator screen in a subagent, analyzes element positions and spacing, and cross-references against official docs. Triggers on "does this look right", "check the layout", "why is this overflowing", "verify the spacing", "the UI looks wrong", "layout issue", "flexbox problem".
    387 repo stars
  24. ▌
    Deeplink Test · ryanthedev bundle
    Test deep links and URL schemes in the iOS Simulator. Reads navigation/linking config, constructs test URLs, fires them via xcrun simctl, and verifies the resulting screen. Triggers on "test deep link", "test this URL scheme", "verify navigation to", "does deeplink work", "open URL in simulator", "test universal link".
    387 repo stars
  25. ▌
    Clarify · ryanthedev bundle
    Decomposes underspecified requests by classifying gaps (missing info, ambiguity, false premises) and generating targeted clarifying questions. Produces a confirmed problem statement before any implementation begins. For sharpening a request that already exists; not for open-ended requirement discovery from a vague idea (use the research command).
    387 repo stars
  26. ▌
    Planning · ryanthedev
    Implements the Standard/Full planning pipeline for Medium and Complex tasks: multi-step discovery, phase decomposition with skill matching, cross-cutting concerns, and plan emission with Gate fields.
    387 repo stars
  27. ▌
    Cc Debugging · ryanthedev bundle
    Applies Code Complete's scientific debugging method: STABILIZE → LOCATE → HYPOTHESIZE → EXPERIMENT → FIX → TEST → SEARCH. For active bug investigation, not QA process design or test coverage planning (use cc-quality-practices).
    387 repo stars
  28. ▌
    Code Standards · ryanthedev bundle
    Generates or updates docs/code-standards.md by scanning the codebase for actual conventions. Produces an example-rich standards file optimized for LLM consumers, grounded in the project's real patterns. Not for auditing one file's naming, comments, or clarity (use code-clarity-and-docs).
    387 repo stars
  29. ▌
    Welc Legacy Code · ryanthedev
    Safely modifies untested legacy code by getting it under test first: characterization tests, seam identification, sprout/wrap techniques, and pinch-point testing before any production changes. Not for refactoring code that already has test coverage (use cc-refactoring-guidance).
    387 repo stars
  30. ▌
    Gof Design Patterns · ryanthedev bundle
    Maps code symptoms — exploding subclass combinations, switch-on-type dispatch, tangled object construction, incompatible interfaces, one-to-many update cascades — to the matching Gang of Four pattern, then loads that pattern's structural recipe from its 23 reference files. For selecting and implementing a design pattern; not for system-level boundaries (use ca-architecture-boundaries) or module interface depth (use aposd-designing-deep-modules).
    387 repo stars
  31. ▌
    Cc Quality Practices · ryanthedev bundle
    Applies Code Complete's QA process design: selects defect-detection techniques by phase, sizes the test suite, and designs review and inspection processes. For QA planning and process design, not active bug investigation (use cc-debugging).
    387 repo stars
  32. ▌
    Code Clarity And Docs · ryanthedev bundle
    Audits and improves code clarity and documentation using APOSD's obviousness rules: naming quality, comment accuracy, AI-facing doc completeness, and the comments-first workflow for new code. Not for generating project-wide convention docs (use code-standards) or structural simplification of the code itself (use aposd-simplifying-complexity).
    387 repo stars
  33. ▌
    Cc Control Flow Quality · ryanthedev bundle
    Audits and restructures control flow using Code Complete's nesting, cyclomatic complexity, loop design, guard-clause, and boolean simplification rules. Covers deep nesting, loop exit design, index naming, and callback chains. For statement-level flow inside a routine; not for routine/class structure (use cc-routine-and-class-design) or staging a broader refactor (use cc-refactoring-guidance).
    387 repo stars
  34. ▌
    Cc Refactoring Guidance · ryanthedev bundle
    Guides safe refactoring using Code Complete's fix-first-then-refactor discipline: decides between refactor, rewrite, and fix-first; enforces separate commits; applies small-change rigor to high-error-rate one-liners. Not for diagnosing the bug itself (use cc-debugging), transforming working code's complexity (use aposd-simplifying-complexity), or untested legacy code (it routes to welc-legacy-code).
    387 repo stars
  35. ▌
    Cc Defensive Programming · ryanthedev bundle
    Applies Code Complete's defensive programming rules: barricade design, assertion vs error-handling selection, input validation policy, and correctness-vs-robustness strategy for the current context. For hardening code at trust boundaries; not for diagnosing an active failure (use cc-debugging) or post-completion verification (use aposd-verifying-correctness).
    387 repo stars
  36. ▌
    Performance Optimization · ryanthedev bundle
    Applies measure-first performance optimization: profiles to find hot spots, applies algorithm and data-structure improvements before micro-optimizations, and validates each change prevents regression. For single-process code tuning; not for correctness bugs (use cc-debugging) or concurrency, distributed, and real-time tuning (explicitly out of scope).
    387 repo stars
  37. ▌
    Cc Pseudocode Programming · ryanthedev bundle
    Structures routine design through pseudocode-first iteration: clarifies naming and purpose before any code, catches design flaws cheaply, and prevents compile-debug loops on poorly understood routines. For designing a routine before writing it; not for assessing routines that already exist (use cc-routine-and-class-design).
    387 repo stars
  38. ▌
    Ca Architecture Boundaries · ryanthedev
    Applies Clean Architecture's dependency-direction and SRP-by-actor rules to system-level boundary design: separates business logic from infrastructure, identifies actor-coupling risks, and enforces inward-pointing dependency arrows. For system scope (multiple components, layers, or services), not routine or module scope (use cc-routine-and-class-design).
    387 repo stars
  39. ▌
    Aposd Verifying Correctness · ryanthedev bundle
    Verifies implementation completeness across functional correctness, error handling, concurrency, and security dimensions using APOSD's post-implementation checklist. Run after a coding task is nominally complete, not during active bug investigation (use cc-debugging).
    387 repo stars
  40. ▌
    Cc Routine And Class Design · ryanthedev bundle
    Applies Code Complete's routine and class design rules at the routine level: cohesion classification, parameter-count thresholds, LSP inheritance verification, and containment-vs-inheritance decision. For routine and class scope, not system architecture (use ca-architecture-boundaries).
    387 repo stars
  41. ▌
    Build Doctrine · ryanthedev bundle
    Implements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: for each Done-When item, write a failing test first, then the minimum code to make it pass (red-green).
    387 repo stars
  42. ▌
    Aposd Designing Deep Modules · ryanthedev
    Guides module and API design using APOSD principles: generates multiple design alternatives, compares them on information hiding and interface depth, and produces a documented design decision. For creating new module/API design; not for assessing existing designs (use aposd-reviewing-module-design) or routine-level design (use cc-routine-and-class-design).
    387 repo stars
  43. ▌
    Aposd Simplifying Complexity · ryanthedev bundle
    Transforms complex code by applying APOSD's pull-complexity-downward principle: resolves error hierarchies, collapses configuration, and moves caller-side logic into modules. Produces edited code; not for assessment-only review (use aposd-reviewing-module-design) or designing new modules from scratch (use aposd-designing-deep-modules).
    387 repo stars
  44. ▌
    Aposd Reviewing Module Design · ryanthedev bundle
    Assesses existing module and interface design for complexity symptoms: information leakage, shallow interfaces, pass-through layers, and unknown unknowns. Produces a structured assessment — not transformations (use aposd-simplifying-complexity to edit) and not new-design generation (use aposd-designing-deep-modules).
    387 repo stars
  45. ▌
    Placeholder Skill · ryanthedev
    Placeholder skill directory required by skill-eval's run_eval tool signature. This benchmark runs configurations=['without_skill'] only — we are measuring raw model tiers, not a skill — so this file's content is never mounted or read by a subject session.
    387 repo stars
  46. ▌
    Distributed Systems Design · ryanthedev bundle
    Guides distributed system design using a structured 4-step framework: scope, high-level design, deep dive, wrap-up. Two modes: CHECKER audits existing designs for missing components, wrong tradeoffs, and anti-patterns. APPLIER walks through designing systems step-by-step with clarifying questions, component selection, and scaling strategies. Covers 15 system designs (rate limiter, consistent hashing, key-value store, unique ID generator, URL shortener, web crawler, notification system, news feed, chat system, search autocomplete, YouTube, Google Drive, scaling foundations, estimation, interview framework) plus cross-cutting techniques and review checklists. Triggers on: system design, distributed system design, design a system, design a distributed, scale system, architecture review, high-level architecture, back of envelope, capacity planning, design with load balancer, database sharding strategy, caching strategy for scale, CDN architecture, message queue design, microservices system design, API system desi
    387 repo stars