Provides a systematic, research-driven workflow for implementing new Vibe components - for the @vibe/core library (located in "packages/core") - from initial research through final validation. Emphasizes studying existing patterns, following established conventions, and systematic progression through types, component implementation, styling, testing, and documentation to ensure consistency and quality.
6958mo agoReviewMountCreate a free account to mount
Use this rule to get a high-level project overview, identify the core function of each crate, understand major subsystems, and find the entry-point documentation for components.
1719mo agoReviewMountCreate a free account to mount
User Education & Support Specialist. Use this agent to generate FAQs, troubleshoot from code logic, and manage documentation as a first line of defense. It turns technical complexity into accessible guides for users.
224mo agoReviewMountCreate a free account to mount
Founder Operating Context. Use to create or update the canonical founder/startup context document so every fundraising, growth, product, and recruiting workflow runs on concrete company facts instead of generic assumptions.
224mo agoReviewMountCreate a free account to mount
Create or update a reusable product marketing context document with positioning, audience, ICP, use cases, and messaging. Use at the start of a project to avoid repeating core marketing context across tasks.
224mo agoReviewMountCreate a free account to mount
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
224mo agoReviewMountCreate a free account to mount
Prevent content duplication in documentation, reports, and code. Check for existing content before creating new. Consolidate duplicates to single source of truth.
110mo agoReviewMountCreate a free account to mount
No unconfirmed assumptions - every factual claim the founder or a user will read is confirmed by a source, test or measurement, or cut, or registered in docs/ASSUMPTIONS.md and labelled. Use when writing any document, copy, report, estimate or recommendation, and when reviewing one.
1616d agoReviewMountCreate a free account to mount
Comprehensive guide for base components in `@vibe/core` library (BaseInput, BaseList, BaseListItem, InfoText, FieldLabel). Documents their usage patterns, accessibility requirements, form integration patterns, and what consumers need to provide for optimal accessibility and UX. These components serve as foundational building blocks for complex UI components like dropdowns, text fields, and other form controls. Those components are internal, for developing components in Vibe, and are not intended to be exported from the `@vibe/core` library.
6958mo agoReviewMountCreate a free account to mount
Every derived figure (a total, a price, a score, a status) is computed in exactly one place and read everywhere; documents never carry hand-typed counts. Use when adding any number a user or the founder will see.
1616d agoReviewMountCreate a free account to mount
Trigger for the docs-page-authoring skill: load it before writing or editing a README or any other documentation page, and when a change adds or renames an option, an error, or a supported version.
Author Diagrammer JSON for the Diagrammer viewer. Use whenever the user asks for a mind map, concept map, flowchart, tree, dependency graph, ER diagram, or timeline. Output a single JSON document conforming to the schema below.
116mo agoReviewMountCreate a free account to mount
How to word anything the founder reads or answers - questions, grilling rounds, approvals, decisions, summaries, reports - at the technical level saved in project.toml [owner] level (non-technical, basics or technical). Use before writing any message or document for the founder.
1616d agoReviewMountCreate a free account to mount
Hypothesis-driven debugging protocol — reproduce, isolate, hypothesize, test, fix, document. Apply when debugging a failure. Find the root cause, not a workaround.
Generate and maintain project documentation from the code (README, API reference, architecture notes, setup docs). Re-runnable to keep docs in sync as the code changes.
Full expert review protocol. 8-expert, 2-wave deliberation for comprehensive codebase and documentation review. Invoke before major milestones, after shipping feature clusters, or before staging/production deployment.
Full expert review protocol. 8-expert, 2-wave deliberation for comprehensive codebase and documentation review. Invoke before major milestones, after shipping feature clusters, or before staging/production deployment.
Use when designing a database schema, writing migrations, reviewing SQL queries, or choosing between relational and document models — covers naming, index strategy, migration safety, N+1 prevention, and transaction boundaries.
The legal agent's method - read the founder's playbook and the region packs, grade each checklist item GREEN, YELLOW, RED or UNSETTLED with a cited and dated source, draft documents flagged for counsel, escalate. Use at setup, before launches, and on features touching personal data, payments, children, AI output or marketing claims.
1616d agoReviewMountCreate a free account to mount
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md those are already markdown, use WebFetch directly.
224mo agoReviewMountCreate a free account to mount
mondaycomCursor rule
