the-vibe-company

@the-vibe-company source repo

23 skills
0 followers
1 day ago last updated

▌
Granite 2 · the-vibe-company
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.

0
installs
▌
Debug Companions Prod 2 · the-vibe-company bundle
Read-only production debugging for the Companions runtime on Railway and box.ascii.dev. Use when production box launches fail, a chat dies or stalls while waiting for input, turns sit queued or interrupted, a Companion appears to reply forever, /healthz is unhealthy, or an operator needs Railway deployment status, redacted runtime logs, provider Box inventory, or named read-only PostgreSQL runtime queries. Every script redacts credentials; the only mutation is a double-gated service restart.

0
installs
▌
Integration Nextjs App Router · the-vibe-company bundle
PostHog integration for Next.js App Router applications

0
installs
▌
Granite · the-vibe-company bundle
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.

0
installs
▌
Granite Lint · the-vibe-company
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.

0
installs
▌
Vault Garden · the-vibe-company
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.

0
installs
▌
Granite Brief · the-vibe-company
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.

0
installs
▌
Granite Capture · the-vibe-company
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.

0
installs
▌
Granite Compile · the-vibe-company
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.

0
installs
▌
Vanish Connect Upgrade · the-vibe-company bundle
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.

0
installs
▌
Design Frontend Dev · the-vibe-company bundle
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states, accessibility, responsive behavior, visual hierarchy, UX copy, motion, design systems, anti-pattern detection, and AI-looking UI cleanup. This clean Companion edition is agent-only: no CLI, no hooks, no live mode, no install commands, no external commercial workflow.

0
installs
▌
Vanish · the-vibe-company bundle
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.

0
installs
▌
Vanish Publish Site · the-vibe-company bundle
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.

0
installs
▌
Vanish Upload Files · the-vibe-company bundle
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.

0
installs
▌
Ship Pr Dev · the-vibe-company bundle
Ship PR: credit-aware autonomous pull request readiness workflow. Use when the user asks to ship work, prepare a branch for review, create or update a PR, make CI green, clean up a branch before PR, or produce a PR a human can confidently merge. This skill may edit code, run checks, commit, push, create/update a PR, and iterate on CI, but it keeps Git ownership in the coordinator, delegates bounded work to cheaper host-native workers, uses review-code-dev as the only independent read-only review gate, waits for all visible latest-SHA CI to be green, runs capture-learning-tools report-only, and never merges.

0
installs
▌
IOS Product Dev · the-vibe-company bundle
Own end-to-end native iOS product work in SwiftUI: shape, implement, and verify beautiful, accessible Companion features while preserving the shared API and platform boundaries. Use for iOS feature work, product-facing UI changes, and native client reviews; route pure visual design or build-only requests to the focused skills.

0
installs
▌
Review Code Dev · the-vibe-company bundle
Independent, credit-aware local code review for any repository. Use when the user asks to review code, validate local changes, run a pre-commit or pre-PR check, inspect uncommitted changes, review a branch or commit, perform a security/frontend/design pass, coordinate isolated sub-reviewers, watch new PRs without duplicate reviews, or decide whether a change should block merge. Uses one isolated primary reviewer and only the smallest set of cheaper host-native focused reviewers needed, then returns read-only evidence-backed P0-P3 findings and ignored local artifacts.

0
installs
▌
Companion · the-vibe-company bundle
Use when managing local SKILL.md packages with Companion: validate, publish, update, resolve dependencies, declare secrets, environment variables, or hosted SQLite state tables, query skill state, install updates, audit skills, check workspace versions, or self-update this Companion skill through the Companion workspace API.

0
installs
▌
Xcodebuildmcp CLI · the-vibe-company bundle
Use the official XcodeBuildMCP CLI for deterministic Apple-platform discovery, build, test, simulator run, debugging, logs, screenshots, and UI inspection. Use for tool execution and verification, not for product shaping or SwiftUI architecture.

0
installs
▌
Incident Summary · the-vibe-company bundle
Summarize an incident timeline from logs into a concise postmortem draft.

0
installs
▌
Swiftui Expert Dev · the-vibe-company bundle
Provide focused SwiftUI implementation expertise for native iOS work: state ownership, composition, navigation, concurrency, performance, accessibility, and testability. Use when the product direction is known and the question is how to implement or refactor SwiftUI safely; route product shaping and build orchestration to their owner skills.

0
installs
▌
Debug Companions Prod · the-vibe-company bundle
Read-only production debugging for the Companions runtime on Railway and box.ascii.dev. Use when production box launches fail, a chat dies or stalls while waiting for input, turns sit queued or interrupted, a Companion appears to reply forever, /healthz is unhealthy, or an operator needs Railway deployment status, redacted runtime logs, provider Box inventory, or named read-only PostgreSQL runtime queries. Every script redacts credentials; the only mutation is a double-gated service restart.

0
installs
▌
Capture Learning Tools · the-vibe-company bundle
Turn technical conversations, bugs, CI failures, review comments, and repeated agent mistakes into durable project improvements. Use when the user asks what should be automated, documented, tested, added to AGENTS.md/CLAUDE.md, wired into CI, or changed so the same issue does not happen again. This skill is for both non-technical and technical users: it explains the learning in plain English, inspects the repository, chooses the right prevention layer, proposes changes first, and only edits project files when explicitly asked.

0
installs

23 published skills