All authors
Claude Skills by ZEST-im
github.com/ZEST-im10 skills0 installs9 views
- Vibe DesignBuild the landing page and key screens as self-contained HTML and look at them in a browser before any implementation starts. Use when a screen, landing page, or UI flow is about to be built, or when vibe-planning reaches its screens stage.Votes: 0GitHub stars: 6
- Vibe HarnessVibe Engineering workflow for Claude Code and Codex. Use for the bare commands ss, qq, or cc; /vibe-harness commands; phase scope; kanban task tracking; work reports; and mandatory post-push review.Votes: 0GitHub stars: 6
- Vibe PlanningProject kickoff planning — walks a developer through gated stages, from north star to a scaffolded project, asking one question at a time. Use when starting a new project, product, or major subsystem and the planning work has to happen alongside the building.Votes: 0GitHub stars: 6
- Vibe ReviewReviews your own work the way a CTO reviews a team member — evidence-based, unsparing, tracking repeated failures across weeks. Weekly scored review, a short daily pass on yesterday's output, and a monthly review left in the project as markdown so later sessions and agents can read it. Use at the start of a day, at the end of a week, at the end of a month, or when you want an outside read on what you have actually shipped.Votes: 0GitHub stars: 6
- Vibe DebugFind the root cause before changing anything — for a bug, a test failure, a check that went red, or behaviour nobody can explain. Use when the cause is not yet known, when a previous fix did not hold, or when the same symptom has come back.Votes: 0GitHub stars: 6
- Vibe AaApplication architecture — module boundaries, dependency direction, API and interface contracts, and the development standards that keep parallel work from colliding, enforced by a check that fails when a boundary is crossed. Use when splitting code into modules or services, when adding a feature that touches several parts, when agents or developers keep editing the same files, when imports start tangling, or when vibe-sa hands off application design.Votes: 0GitHub stars: 6
- Vibe DaData architecture — conceptual, logical, and physical data models, a standard glossary of terms and codes, system of record per entity, data flows, sensitivity classification, retention, and migration rules. Use when designing or changing a schema, adding entities, integrating a data source, handling personal data, when the same thing is called three different names in the code, or when vibe-sa hands off data design.Votes: 0GitHub stars: 6
- Vibe SaSolution architecture — turns requirements into one coherent system shape (context, quality targets, build-vs-buy, the few decisions that are expensive to reverse) and decides which of application, data, and technical architecture need deeper work. Use when a project moves from planning to building, when a new subsystem or integration is proposed, when someone asks "how should we build this", or before any change that crosses more than one part of the system.Votes: 0GitHub stars: 6
- Vibe TaTechnical architecture — where the system runs, how big it must be (sized with shown arithmetic), environments, redundancy, backup and restore that has actually been tested, network and secrets, observability, and cost. Use when deciding hosting or cloud setup, preparing a first deployment or a pilot-to-rollout step, estimating capacity or monthly cost, setting availability targets, or when vibe-sa hands off infrastructure design.Votes: 0GitHub stars: 6
- Vibe ArchitectRun the full architecture pass — solution, application, data, and technical — in order, and score the handoff predictions afterwards. Use when someone asks for "the architecture" of a system rather than one specific view, when onboarding onto an unfamiliar codebase, or before a change large enough that no single pass would see all of it. To run one view only, invoke vibe-sa, vibe-aa, vibe-da, or vibe-ta directly.Votes: 0GitHub stars: 6