Claude Skills by darkroomengineering

Expert guidance and advice from Oracle. Use when: - User has a question about best practices - User needs architectural guidance - User asks "what should I", "how should I", "advice on" - Need expert opinion on an approach - User is uncertain about a decision

Feature implementation workflow. Use when the user wants to: - "build a", "create a", "implement", "add feature" - build a new page, component, feature, integration - create something from scratch - add new functionality to the app

Create React components following Darkroom standards. Use when: - User says "create component", "new component", "add component" - User wants to build a UI element, widget, or reusable piece - User mentions a component name like "Button", "Header", "Card"

Save session state for later resumption. Use when: - User says "done for today", "ending session", "save state" - Context is getting full (80%+) - User is taking a break - Before context compaction - User mentions "handoff", "pause work", "wrapping up"

Browser debugging with agent-browser CLI. Use when: - User mentions "screenshot", "visual bug", "inspect element" - User asks "what does it look like", "see the page" - Need to debug browser rendering, layout, or visual issues - User wants to test UI in browser - E2E debugging or visual verification

Discovery interview to understand requirements. Use when: - User says "help me figure out", "what do I need", "define requirements" - Scope is unclear or ambiguous - Starting a new feature with vague requirements - User needs help clarifying what they want

Fetch latest documentation for libraries and frameworks. CRITICAL - AUTO-INVOKE when: - User wants to implement with ANY external library (GSAP, Lenis, Three.js, Framer, Radix, etc.) - User asks "how to use X", "X docs", "X API", "X reference" - Before writing ANY code that uses external packages - User mentions library names: gsap, lenis, three, framer, motion, radix, sanity, zustand MANDATORY: Never assume API knowledge. Always fetch current docs first.

Dynamic effort level management. Use when: - User mentions "think harder", "be thorough", "quick fix", "max effort" - Task complexity changes mid-session - Need to optimize for speed vs depth - User says "slow down", "speed up", "think more"

Codebase exploration and understanding. Use when the user asks: - "how does X work?", "where is X?", "find X", "understand X" - "what files handle X?", "show me the X implementation" - "navigate to X", "explore the codebase" - any question about code structure, architecture, or implementation details

Bug investigation and resolution workflow. Use when the user mentions: - "fix", "broken", "not working", "bug", "error", "issue", "failing" - debugging, troubleshooting, investigating problems - something that used to work but doesn't anymore - errors in console, build failures, test failures

Create custom React hooks following Darkroom standards. Use when: - User says "create hook", "new hook", "custom hook" - User wants to extract logic into a reusable hook - User mentions "use" prefix like "useAuth", "useScroll"

Initialize a new project with Darkroom standards. Use when: - User says "new project", "start project", "initialize", "setup project" - User wants to create a new Next.js, React, or web app - User mentions "satus" or "starter template"

Persistent memory system for storing and recalling learnings across sessions. AUTO-INVOKE THIS SKILL when you: - Fix a non-obvious bug (store as "bug") - Discover a useful code pattern (store as "pattern") - Encounter a gotcha or edge case (store as "gotcha") - Find a useful tool/library feature (store as "tool") - Make a performance optimization (store as "perf") - Discover configuration that solved a problem (store as "config") - Make an architecture decision with rationale (store as "arch...

Set up Lenis smooth scroll. Use when: - User mentions "smooth scroll", "lenis", "scroll behavior" - User wants to add smooth scrolling to the app - Setting up scroll-based animations

Multi-agent task orchestration for complex features. Use when: - User has a complex, multi-step task - Task requires multiple agents working together - User says "coordinate", "orchestrate", "complex task" - Work involves planning, implementation, testing, AND review

Visual QA validation with agent-browser. Use when: - User asks to "validate", "check visually", "QA check" - After creating or modifying components - Before PR submission - User mentions "accessibility", "a11y", "contrast", "touch targets" - User wants to verify UI looks correct

Code refactoring workflow. Use when: - User says "refactor", "clean up", "reorganize", "restructure" - Code needs improvement without changing behavior - User wants to improve code quality, readability, or performance - Technical debt needs addressing

Resume from a previous session handoff. Use when: - User says "resume", "continue where we left off", "pick up where" - Starting a new session after a break - User mentions "last session", "previous work"

Code review for quality, security, and best practices. Use when: - User asks to "review", "check", "look at" code - Before merging, committing, or shipping - User mentions PR, pull request, changes, diff - User wants feedback on implementation - After implementing a feature (self-review)

Shipping pipeline: build, verify, and create PR. Use when: - User says "ship it", "create PR", "open PR", "ready to merge" - User says "/pr", "/ship", "push and PR" - After implementation is complete and needs to be shipped - User wants to verify and publish changes

Agent Teams orchestration for multi-instance parallel work. Use when: - User mentions "use teams", "parallel agents", "split work", "fan out" - Task has 3+ independent workstreams - Large-scale refactoring across unrelated files - User says "divide and conquer", "multi-instance"

Testing workflow - write and run tests. Use when: - User says "test", "write tests", "add tests", "run tests" - User mentions "coverage", "unit test", "integration test" - After implementing a feature (tests should follow) - Before shipping or merging code

TLDR code analysis for token-efficient codebase understanding. AUTO-INVOKE when: - User asks "who calls X", "what affects X", "find implementation" - Need to trace dependencies, call graphs, or data flow - Semantic search for code by meaning (not exact string) - Understanding large codebases efficiently - Before reading any large file (use context first) - Debugging "why is X null/undefined here" - Before refactoring (impact analysis) PREFER TLDR over raw file reads - 95% token savings.

Check package versions before installing. CRITICAL - AUTO-INVOKE when: - About to install any package (bun add, npm install) - User asks about "latest version", "update package" - Before implementing with any library MANDATORY: Never install packages without checking version first.