dotfiles

Answer a question about a GRACE-lite project using full project context. Use when the user has a question about the codebase, architecture, modules, or implementation — loads all GRACE artifacts, navigates the knowledge graph, and provides a grounded answer with citations.

Debug an issue using GRACE-lite semantic navigation. Use when encountering bugs, errors, or unexpected behavior - navigate through the graph, verification plan, and semantic blocks to analyze the mismatch and apply a targeted fix.

Bootstrap GRACE-lite for a project. Use when user ask you to initialize project with GRACE-lite.

Synchronize GRACE-lite shared artifacts with the actual codebase. Use targeted refresh after controlled waves, or full refresh after refactors and when you suspect wider drift between the graph, verification plan, and code.

GRACE integrity reviewer. Use for reviews during execution, or full integrity audits at phase boundaries and after broader code, graph, or verification changes.

Применяй когда: пользователь просит проверить, переписать, очеловечить или оживить русскоязычный текст со следами генерации ИИ (ChatGPT, Claude, Gemini, Grok, DeepSeek, GPT-5, Qwen, любая нейросеть). Активируй для запросов: «очеловечь», «сделай живым / естественным», «убрать гпт-шность», «звучит как нейросеть», «AI-детектор для русского», «проверить на ИИ», убрать штампы / клише / канцелярит / шаблонные обороты / эмодзи-списки 🚀 / неуместное длинное тире / льстивый тон / фабрикованные источники. Также при видимых маркерах копирования из чат-бота: `:contentReference`, `?utm_source=chatgpt.com`, `oai_citation`, `grok_card://`, `vertexaisearch`, `turn0search`. Не применяй: текст не на русском, исходный код / скрипты (даже про NLP), юридические документы (канцелярит = жанр), художественная проза / поэзия / резюме (там длинное тире, ритм и сжатость — авторский приём).

Mandatory prerequisite for ALL OpenSpec operations — load this BEFORE any openspec-* skill. Use when running /opsx-apply, /opsx-propose, /opsx-verify, /opsx-archive, /opsx-explore, /opsx-sync; running `openspec status`, `openspec list`, `openspec instructions`; reading files under `openspec/changes/`; or doing any OpenSpec stage (propose, apply, verify, archive, explore, sync).

Diagnose and resolve permission denials when opencode runs inside a nono security sandbox. Use this when a tool call, shell command, or file operation fails with "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied errors.

UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.

Search public GitHub code with the grep.app MCP CLI to find real implementation patterns, concrete API usage, regex-based code matches, and repository-scoped examples. Use when a task needs literal code search rather than documentation search, especially to verify how libraries, frameworks, config files, or language features are used in real projects.