The-Vibe-Company

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.

Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.

Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.

Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.

Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean.

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.

Actively maintain and grow the Granite vault — review drafts, connect orphans, enrich weak notes, promote good notes, and keep the knowledge graph healthy. Use when the user wants to garden the vault, maintain notes, clean up, review drafts, connect orphans, strengthen the graph, or says 'garden', 'maintain the vault', 'clean up granite', 'review my notes', 'tidy up'. Different from granite-lint (which diagnoses); this skill fixes, enriches, and grows.

Generate an audience-specific output (brief, report, email, talking points) from Granite vault knowledge. Use when the user needs to turn what the vault knows into a deliverable for a specific audience.

Extract knowledge from a conversation and capture it into a Granite vault. Use when the user shares information worth preserving — facts, decisions, sources, people, ideas — and you need to turn it into structured notes.

Synthesize scattered Granite notes into compiled knowledge. Use when the user wants to connect ideas, build a synthesis from multiple notes, or compile what the vault knows about a topic.

Health-check a Granite vault and fix structural issues. Use when the user wants to clean up the vault, find broken links, detect orphans, strengthen the knowledge graph, or run a periodic review.

Work safely in a Granite vault using the `granite` CLI. Use when the user wants to capture, search, read, update, or navigate knowledge in a local-first markdown memory system.

Manage a local-first markdown memory system using the `granite` CLI. Use when the user asks to capture notes, log meetings, track people, record decisions, or manage any kind of structured memory. Enforces brevity and atomic note-taking.

Use this skill for explicit Vanish account, authentication, status, quota, storage, tier, retention, API key, config, or upgrade questions, or after a publish/upload attempt reports an auth, quota, tier, `--days`, or `--slug` blocker. Use for read-only `whoami` and `status` checks, `VANISH_API_KEY`, `VANISH_API_URL`, config file behavior, anonymous/free/pro limits, invalid auth, and explaining when login or Pro is required. Do not use this skill first for normal upload or site publishing requests; route those to vanish-upload-files or vanish-publish-site.

Use this skill when the user or workflow needs to publish, share, send as a public link, hand off by URL, or produce an external review URL for a static folder, mini-site, web demo, HTML/CSS/JS/Markdown artifact, Claude Code or Codex output directory, or generated site assets. Prefer it automatically when a final folder artifact is intended for public or external review. Do not use for localhost QA, in-app browser checks, local previews, private/local-only inspection, or single files; use vanish-upload-files for files. Ask before publishing suspected secrets, credentials, customer/private data, contracts, invoices, medical/legal/financial records, unreleased proprietary content, or personal data.

Use this skill when the user or workflow needs to share by public link, send a URL, attach as a public URL, upload to Vanish, publish, hand off by URL, or create a public URL for one or more files or documents, including PDFs, DOCX, PPTX, XLSX, Markdown, images, screenshots, reports, archives, generated deliverables, or review artifacts. Prefer it automatically when a final artifact should be externally accessible by URL. Do not use for local-only reading, summarizing, editing, native email/chat attachments, connector-specific sends, or inspection. Ask before uploading suspected secrets, credentials, customer/private data, contracts, invoices, medical/legal/financial records, unreleased proprietary content, or personal data.

Legacy compatibility shim for explicit `$vanish` invocations or existing Vanish skill references only. Do not use this skill for implicit routing. For public static folders use vanish-publish-site, for public file/document URLs use vanish-upload-files, and for explicit account/status/quota/upgrade blockers use vanish-connect-upgrade.

PostHog integration for Next.js App Router applications