darasoba
- 3 skills
- 0 followers
- 17 hours ago last updated
- ▌ Design Engineer · darasobaBuild interfaces with design engineering craft — the intersection of design and code. Use this skill when the user asks to build UI components, interactive elements, animations, micro-interactions, or polished web experiences. Triggers on mentions of "design engineer", "interaction design", "micro-interactions", "craft", "polish", "delight", "animation", "motion design", "haptics", "toast", "command palette", "design system components", or requests for interfaces that feel alive, responsive, and meticulously detailed. This skill should also be used when the user wants to add invisible details, fine-tune interactions, or make something "feel right". Complements the frontend-design skill by focusing specifically on interaction quality, motion, and engineering craft.
- ▌ Fable Reasoning · darasoba bundleElite reasoning and coding discipline distilled from Claude Fable 5's problem-solving patterns. Load at the START of any non-trivial task — debugging, implementing features, refactoring, architecture decisions, code review, or multi-step investigations. Raises reasoning quality by enforcing hypothesis-driven thinking, evidence-based claims, calibrated effort, root-cause fixes, and adversarial self-verification. Triggers on - "debug", "fix", "implement", "build", "refactor", "why is this failing", "design", "investigate", or any task where being wrong is expensive.
- ▌ Engineering Manager · darasoba bundleSenior engineering-manager / principal-engineer persona for modern full-stack web apps — the technical lead who owns architecture, raises the quality bar, and is the final reviewer before code ships. Has deep, current (2026) command of the stack: Next.js 16 App Router, React 19, TypeScript, Tailwind CSS 4, Supabase (@supabase/ssr + Row Level Security), Vitest, Playwright, and Vercel (Fluid Compute). USE THIS SKILL whenever the work involves designing a feature or system, making or recording an architecture/tradeoff decision, reviewing or approving a change before merge, deciding "is this the right approach / is this scalable / can we ship this", scoping technical work, onboarding to a codebase, or any question that benefits from a staff-level engineer's judgment about this stack. Also trigger on: "review this", "is this right", "how should we build/structure X", "design", "architecture", "tradeoffs", "approve", "sign off", "ship it", "is this safe", server/client boundaries, Server Actions, RLS, caching, time