Claude Skills by Podbay-Cloud

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Implement tasks from an OpenSpec change (Experimental)

Archive a completed change in the experimental workflow

Enter explore mode - think through ideas, investigate problems, clarify requirements

Propose a new change - create it and generate all artifacts in one step

Sync delta specs from a change to main specs

Write a durable handoff note before this pod is interrupted (update/suspend) so the next session — possibly a different agent — can pick up without re-deriving anything. Use when asked to hand off, or before you expect to be interrupted.

Always go, never assume — the leading work driver. Continuous autonomous execution with a visible register, permission lanes, async questions, and self-scheduled continuation. Use in EVERY session; it governs how all other work happens.

Fetch and research public web content from a pod without evading anyone — walk the ladder (official API → direct fetch → archive → reader service → the owner's relay) and report honestly when a target is fortified. Also covers the relay's egress tunnel ($PODBAY_RELAY_PROXY) for crawlers, scripts and Playwright that must fetch through the owner's connection with a live DOM. Use for lead/market research, reading a prospect's or competitor's site, extracting landing/product pages, monitoring pag...

Fix the iOS keyboard "composer stranded at the top / page scrolls up" bug in any mobile web app with a bottom-fixed input. Use whenever you build or touch a chat/message/comment/search UI whose input sits at the bottom of a full-height layout.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Orient yourself in an UNFAMILIAR existing codebase before making changes. Use at the start of any byo-project session and whenever you land in a repo you haven't mapped yet: read its docs, map the structure, detect the stack, and — critically — find and verify the install / dev / test commands. Produces a short orientation you report back, and (only if the repo lacks one) a starter AGENTS.md. Do NOT use for greenfield/scaffolding — this is for a repo that already exists.

Push a branch and open a pull request from a headless pod using the gh CLI, with a MANDATORY confirmation gate before anything leaves the machine. Use when the user wants to open a PR for work on THEIR OWN repo. Pairs with finishing-a-development-branch (which prepares the commit). Never force-pushes, never runs `git add .`, never opens a PR without an explicit yes.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Drive the "Ask Your Docs" engagement end to end — the staged flow that turns the user's documents into a live, grounded, shareable bot, with the agent leading and a living ~/work/PLAN.md. Use at the start of a doc-qa session and to decide the next step at any point. Lead the user through it; don't wait to be told each move.

Get the user's documents INTO the bot cleanly — accept common formats (txt/md/pdf/docx/html), extract readable text, chunk it well for retrieval, and report back what was actually indexed. Use when the user wants to add their docs, when an upload fails or indexes badly, or when answers are missing content you'd expect (usually an ingestion problem, not a retrieval one).

The integrity spine of an "Ask Your Docs" bot — make it answer ONLY from the user's retrieved documents, attach citations to every claim, and say "I don't know" when the docs don't support an answer. Use when building, tuning, or debugging the chat/answer route, the system prompt, or anytime an answer looks invented, uncited, or over-confident. A wrong-but-confident answer is worse than "I don't know."

Make the bot's answers actually good — evaluate and improve RETRIEVAL (does the right passage come back for a real question?) and tune the answer behavior. Use after docs are loaded, whenever answers are wrong/thin/miss content that IS in the docs, or when deciding chunk size / top-k / semantic-vs-keyword search. Test with real questions, don't eyeball the code.

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this wheneve...

Build and maintain a lightweight CRM inside the pod's Next.js app — a leads table + conversation log that is the user's persistent, returnable pipeline. Use when the user is tracking prospects/outreach for the first-10-customers playbook.

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community rese...

When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psyc...

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect researc...

Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.

Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.

QA an analysis before sharing -- methodology, accuracy, and bias checks. Use when reviewing an analysis before a stakeholder presentation, spot-checking calculations and aggregation logic, verifying a SQL query's results look right, or assessing whether conclusions are actually supported by the data.

Monitor a value or source over time and alert only on meaningful change. Use when a job watches metrics, prices, statuses, uptime, inventory, feeds, or any source for thresholds, spikes, drops, or state changes — snapshot, diff, apply thresholds, dedupe, cooldown, and announce recovery.

Implement a described feature end-to-end in this Next.js workspace, then verify it builds. Use when the user asks to add or change a user-facing feature.