Claude Skills by grenzkamm

Decide the house style of the whole product once - module boundaries, how a request runs, where tenant isolation is enforced, where business rules live, error handling, logging, background work, migrations and the test setup. Runs once after planning, so nineteen features do not invent nineteen answers. Writes no code.

Plan a whole SaaS product from a briefing - PRD, feature map with build waves, data model, user journeys, roles and plan gating, app shell, design system and a local dev plan. Plans only, writes no code. Use once at project start.

Turn the plan and the architecture into a repository a developer can actually run - folder skeleton, database and services in containers, migrations, test harness, the quality gate configured with its real thresholds, CI, and env examples. Ends by proving the documented commands work from a fresh clone. The one skill allowed to write configuration and start services.

Decide the house style of the whole product once - module boundaries, how a request runs, where tenant isolation is enforced, where business rules live, error handling, logging, background work, migrations and the test setup. Runs once after planning, so nineteen features do not invent nineteen answers. Writes no code.

Plan a whole SaaS product from a briefing - PRD, feature map with build waves, data model, user journeys, roles and plan gating, app shell, design system and a local dev plan. Plans only, writes no code. Use once at project start.

Turn the plan and the architecture into a repository a developer can actually run - folder skeleton, database and services in containers, migrations, test harness, the quality gate configured with its real thresholds, CI, and env examples. Ends by proving the documented commands work from a fresh clone. The one skill allowed to write configuration and start services.

Decide the house style of the whole product once - module boundaries, how a request runs, where tenant isolation is enforced, where business rules live, error handling, logging, background work, migrations and the test setup. Runs once after planning, so nineteen features do not invent nineteen answers. Writes no code.

Plan a whole SaaS product from a briefing - PRD, feature map with build waves, data model, user journeys, roles and plan gating, app shell, design system and a local dev plan. Plans only, writes no code. Use once at project start.

Turn the plan and the architecture into a repository a developer can actually run - folder skeleton, database and services in containers, migrations, test harness, the quality gate configured with its real thresholds, CI, and env examples. Ends by proving the documented commands work from a fresh clone. The one skill allowed to write configuration and start services.

Decide the house style of the whole product once - module boundaries, how a request runs, where tenant isolation is enforced, where business rules live, error handling, logging, background work, migrations and the test setup. Runs once after planning, so nineteen features do not invent nineteen answers. Writes no code.

Plan a whole SaaS product from a briefing - PRD, feature map with build waves, data model, user journeys, roles and plan gating, app shell, design system and a local dev plan. Plans only, writes no code. Use once at project start.

Turn the plan and the architecture into a repository a developer can actually run - folder skeleton, database and services in containers, migrations, test harness, the quality gate configured with its real thresholds, CI, and env examples. Ends by proving the documented commands work from a fresh clone. The one skill allowed to write configuration and start services.