All authors
Claude Skills by Ghosteken
github.com/Ghosteken205 skills1 installs193 views
- Project ScaffoldingScaffolds a new project's initial file/folder structure, tooling, and config based on its tech stack and project type (a Python service, a Next.js app, a monorepo, a CLI tool, etc.) — asking which stack and project type apply before generating anything, rather than assuming. Use when asked to "scaffold a project", "set up a new [stack] project", "bootstrap this repo", "create the initial structure for", or similar, before meaningful code exists.Votes: 0GitHub stars: 2
- Playwright E2e TestingBuilds and maintains a persistent, CI-integrated Playwright end-to-end test suite for critical user journeys — page objects, fixtures, API-based auth/data setup, network and WebSocket mocking, visual regression, cross-browser coverage, and flake-resistant waiting strategies, scaled to handle complex multi-step and real-time features. Use when a feature needs a lasting, repeatable browser test (not a one-off manual check), when setting up E2E testing for a project, when tests are flaky or slow...Votes: 0GitHub stars: 2
- Product SaasWrites a whole-product PRD for a new app or product idea — starting from a problem statement and idea (optionally grounded in a comparable app the user has seen solve a similar problem, plus any context docs pointed at), gathers the project's fundamentals (app type, high-level tech stack) via AskUserQuestion, suggests a name for the product, proposes core features the user can accept, add to, or refine, lists the external integrations an MVP will need, searches the web for whatever current da...Votes: 0GitHub stars: 2
- Record A DemoRecords a polished, human-paced video walkthrough of a finished, already-QA'd feature via Playwright's screencast API — for stakeholder review, sign-off, or sharing. This is a presentation artifact, not a testing pass. Use when asked to demo, walk through, or record a video of finished work — never for a feature that hasn't already passed verification.Votes: 0GitHub stars: 2
- Slice To IssuesTakes a feature — from its existing implementation doc/PRD, or by searching the codebase and docs itself when none exists — and divides it into a reasonable, feature-driven number of independently verifiable slices (3-4 is the typical default, more when a feature genuinely needs it, never padded to 10-15), each both testable on its own and a substantial real milestone, with acceptance criteria and dependencies. Saves and shows the slice document, then stops — only a separate, explicit go-ahea...Votes: 0GitHub stars: 2