bl1nk-bot

Expert system for scaffolding Gemini CLI extensions. Handles directory structure, manifest files (gemini-extension.json), Skill templates (SKILL.md), and Command templates (.toml).

Use this skill for writing, reviewing, and editing documentation (`/docs` directory or any .md file) for Bl1nk Agents Manager.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Generate a custom checklist for the current feature based on user requirements.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Create a feature branch with sequential or timestamp numbering

Execute the implementation plan by processing and executing all tasks defined in tasks.md

Helps create, edit, and manage custom Qwen Code commands (slash commands). Use this skill whenever the user wants to create a new command, modify an existing command, set up command templates, organize commands into namespaces, or asks about command syntax like @{}, !{}, or {{args}}. Also use when the user mentions "custom commands", "slash commands", "command templates", "command workflows", or wants to automate repetitive AI prompts. If the user has a repetitive task they want to automate with a command, or wants to learn about the commands feature, this skill should be triggered.

Comprehensive writing assistant plugin for novelists and creative writers. Use for story outline management, character tracking, content analysis, Obsidian vault sync, Craft API integration, and Slack notifications. Enables writers to organize plots, analyze narrative structure, detect writing issues, and maintain writing consistency across multiple tools.

Pickle Rick's "God Mode" Implementation Skill. Executes technical plans with rigorous verification. Use when you are ready to write code, run tests, and iterate through implementation phases.No Jerry-work allowed.

Expertise in conducting technical research on codebase tasks and documentation. Use when you need to understand existing implementations, trace data flows, or map codebase patterns.

Expertise in creating detailed, atomic, and safe implementation plans. Use when you need to transform requirements into a step-by-step technical execution strategy.

Activates the Pickle Rick persona. Use this ONLY when the user explicitly requests to start the "Pickle Rick" mode or loop. DO NOT use this for general greetings (e.g., "hi") normal assistance.

Expertise in reviewing implementation plans for architectural soundness, specificity, and safety. Use before implementation to prevent "vague plans" and "messy code."

Pickle Rick's PRD Engine. Use when you need to define the requirements, scope, and goals for a new feature or project before coding to avoid "Jerry-work."

Design and specify banners for CKM projects across all platforms and formats. Activate when the user asks to create, design, or plan banners, social media covers, display ads, web heroes, or print materials. References references/banner-sizes-and-styles.md for the full size catalog and 22 art direction styles.

Identify, map, and optimize all conflicts within a Visual Story Planner StoryGraph. Always activate this skill when the user mentions: "conflict", "tension", "escalation", "antagonist dynamics", "analyze conflicts", "my story lacks tension", "how do conflicts connect", "conflict optimization", "subplot conflicts", or "is my conflict believable". Also use when the user asks why the story feels flat or stakes feel low — conflict analysis is almost always the answer. Produces a conflict map with type classification, escalation health score, interconnection diagram (as text), and specific improvement suggestions ranked by impact.

Expert story structure analysis using bl1nk-visual-mcp. Analyze story text, extract 3-act structure, characters, conflicts, relationships, and validate narrative structure. Activates for analyze story, story structure, story graph, validate story, character extraction, conflict analysis, narrative structure, story validation, three act structure.

Expert story visualization and export using bl1nk-visual-mcp. Export StoryGraph to Mermaid diagrams, Canvas JSON, Markdown, HTML dashboards, and MCP UI dashboards. Activates for export story, export mermaid, export canvas, story dashboard, story visualization, convert to mermaid, story markdown, story html.

Deep structural analysis of story graphs for Visual Story Planner projects. Use this skill whenever the user says "audit", "check structure", "analyze story structure", "is my story balanced", "review my plot", "structural report", or asks for feedback on three-act balance, pacing health, character arc completeness, or conflict escalation. Also activate when the user runs `validate_story_structure` and wants an explanation of results, or when story export output is present and they want a critique. IMPORTANT: Any export action (export_mermaid, export_canvas, export_dashboard, etc.) must be preceded by `validate_story_structure`. If validation reports any issues, surface them with severity levels (error / warning) and require explicit user acknowledgment before continuing to export. Block exports when blocking (error-level) issues exist unless the user explicitly confirms they accept the risk. This skill provides a four-phase audit (Structure → Characters → Conflicts → Pacing) with a scored health report and p

Extract and analyze themes, motifs, and symbolic patterns from story graphs. Always activate when the user mentions: "themes", "motifs", "symbolism", "symbolic meaning", "deeper meaning", "underlying message", "theme analysis", "recurring elements", "patterns in story", "symbolic objects", or asks about "what does this story mean", "what is the message", or "what themes are present". Also activate when user exports or validates story and wants to understand the thematic depth. This skill identifies explicit and implicit themes, tracks motif recurrence, and provides thematic arc analysis — not just a list of tags.

Run, start, build, screenshot, or test the packages/desktop Vite+React app (Visual Story Planner web layer). Drives all 4 views (Editor, Graph, Timeline, Insights) headlessly with Playwright.

(1)Optimize story pacing, emotional arcs, tension curves, and narrative flow for Visual Story Planner StoryGraphs. Always activate when the user says:"pacing", "too fast", "too slow", "emotional arc", "tension build", "story feels flat", "optimize story", "improve flow", "climax doesn't land", "restructure events", "my story drags", or "how do I build tension". Also activate when a structural audit shows ACT_IMBALANCE warnings — arc optimization is the fix. Produces a pacing score, tension curve visualization (ASCII), emotional arc trajectory,and an ordered list of concrete restructuring moves with before/after event counts.

This skill should be used when creating plugins, writing skills, building commands, developing agents, or asking about "plugin development", "create skill", "write command", "build agent", "SKILL.md", "plugin structure", "progressive disclosure".

บันทึกการเรียนรู้ ข้อผิดพลาด และการแก้ไขเพื่อการปรับปรุงอย่างต่อเนื่อง ใช้เมื่อ: (1) คำสั่งหรือการทำงานล้มเหลว (2) ผู้ใช้แก้ไขข้อมูล (3) ผู้ใช้ร้องขอความสามารถที่ไม่มี (4) API หรือเครื่องมือภายนอกล้มเหลว (5) พบแนวทางที่ดีกว่าสำหรับงานที่ทำซ้ำ หรือต้องการทบทวนการเรียนรู้ก่อนเริ่มงานสำคัญ

Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use language-specific skills), or infrastructure setup (use deployment-engineer).

This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.

Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.

Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.

Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

Systematic pre-merge verification workflow for Rust monorepo branches. Check compilation, tests, clippy, grep leftovers, then fix → commit → push → PR. Use when user says "check work done in this branch" or before merging any PR.

Dependency lock and Cargo.lock conflict policy for Rust workspaces. Covers when to update, when to regenerate, manual conflict handling, and merge/sync guidelines to prevent recurring Cargo.lock merge conflicts.

Audit and fix documentation (README, ARCHITECTURE, CHANGELOG) against current codebase while waiting for CI/bot reviews on a PR. Fix factual drift, dead references, and add changelog entries — then commit docs to the same branch.

Daytona sandbox knowledge for answering user questions about remote development environments. Use when the user asks about Daytona, sandboxes, remote execution, cross-platform builds, or needs to run code on cloud infrastructure instead of locally. Provides API details, pricing, troubleshooting, and CLI commands.

Modal.com knowledge for answering user questions about serverless GPU compute, cost comparison with Daytona, and Python-based sandbox workflows. Use when the user asks about GPU access, ML training, Modal pricing, serverless sandboxes, or wants to compare cloud compute options for their Rust/Python projects.

Mandatory project quality workflow for the specgen Rust monorepo. Enforces zero-warning policy, formatting standards, and test compliance. Trigger before any commit, pull request, or completion of a coding task. Also trigger when the user says "check quality", "run QA", or "is it ready?".

Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work. Trigger on first run in any new codebase, after AI-assisted coding sessions, or when user says "clean up", "review quality", "check slop", or "anti-slop".

How to implement a robust MCP server that dispatches domain-specific tool calls to a compiled CLI (e.g., Rust/Go). Use this when building MCP integrations for existing CLI tools, or when platform constraints (like Termux/Android) prevent direct usage of native Node.js database drivers. This skill teaches the 'Generic Dispatcher' pattern to keep the bridge layer thin and performant.

Complete project architecture and structure guide for bl1nk-org monorepo. Use when exploring the codebase, understanding project organization, finding files, or needing comprehensive architectural context. Triggers on architecture questions, directory navigation, "where is X", "how does X work", adding new features, or understanding data flow.

Linear issue management. MUST USE when: (1) user mentions BLNK-xxx issue IDs (e.g. BLNK-0001), (2) user says 'linear', 'linear issue', 'link linear', (3) creating PRs that reference Linear issues. Provides workflows for retrieving issues, updating status, and adding comments.

Complete project architecture and structure guide. Use when exploring the codebase, understanding project organization, finding files, or needing comprehensive architectural context. Triggers on architecture questions, directory navigation, or project overview needs.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

---

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.