start-vibing 4.4.1 → 4.4.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "start-vibing",
|
|
3
|
-
"version": "4.4.
|
|
3
|
+
"version": "4.4.2",
|
|
4
4
|
"description": "Setup Claude Code with 9 plugins, 6 community skills, and 8 MCP servers. Parallel install, auto-accept, superpowers + ralph-loop. e2e-audit 0.2.0 refactor (skill-only, no agents): SessionStart hook + slash command make the skill keyword-invokable (\"e2e audit\", \"roda o e2e\", \"integration test\", \"test coverage gaps\"). Source-first discovery via detect-stack, discover-routes (Next app/pages/Remix/SvelteKit/Nuxt/Astro), discover-api-surface (HTTP handlers, tRPC procedures, GraphQL, server actions, middleware auth), inventory-existing-tests (preserve prior corpus + sha256 drift hash), and detect-uncovered (branch-diff vs origin/main finds changes not covered by existing specs). Report-then-ask between mapping and Playwright run; post-run-feedback report before writing findings. SHOT+TRACE+ASSERT+SOURCE evidence quad per non-meta finding; meta rules (coverage-gap-*, uncovered-*, test-drift, stack-detect, post-run-feedback) exempt. verify-audit.sh enforces schema + quad. Generic (no project leakage). super-design 0.7.0 carries over.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -0,0 +1,4 @@
|
|
|
1
|
+
#!/usr/bin/env bash
|
|
2
|
+
cat <<'EOF'
|
|
3
|
+
{"hookSpecificOutput":{"hookEventName":"SessionStart","additionalContext":"MCP USAGE RULES (non-negotiable for this project):\n\n1. sequential-thinking — You MUST invoke `mcp__sequential-thinking__sequentialthinking` BEFORE proposing a solution whenever the task involves: multi-step implementation, architecture/design decisions, debugging a non-trivial bug, refactor planning, trade-off analysis, or any request where the path is not obvious in one step. Do not skip it because the answer 'feels clear' — use it to externalize the plan, then act. Skip ONLY for: trivial single-file edits, pure lookups, direct factual questions, or formatting/typo fixes.\n\n2. context7 — You MUST invoke `mcp__context7__resolve-library-id` followed by `mcp__context7__query-docs` BEFORE writing or modifying code that uses ANY external library, framework, SDK, API, or CLI tool — including well-known ones (React, Next.js, Mongoose, Zod, Tailwind, shadcn, TanStack Query, Playwright, Vitest, Bun, Express, Prisma, etc.). Your training data may be stale; context7 returns current docs. Skip ONLY for: pure language features (vanilla TS/JS), project-internal code with no library surface, or refactors that don't touch library APIs.\n\n3. Order of operations for a typical feature task: sequential-thinking (plan) → context7 (verify library APIs) → implement → quality gates. Do not invert.\n\n4. If you catch yourself about to write code without having called context7 for a library you're importing, STOP and call it first. If you catch yourself proposing a multi-step plan without sequential-thinking, STOP and call it first.\n\n5. These MCPs are already connected in this project (.mcp.json). There is no setup cost — just call them."}}
|
|
4
|
+
EOF
|