project-context

Project context automation defines your project's nature, technology stack, and implementation principles upfront, eliminating manual configuration for each new TypeScript project. This Skill provides templates that conform to LLM-driven implementation, Vitest testing, Biome quality practices, and YAGNI discipline, accelerating setup across new projects.

Customize project context by defining project nature, selecting your technology stack, establishing implementation principles, and choosing appropriate architecture patterns. This Skill guides configuration of environment setup and architecture selection to align with Claude Code-driven implementation and quality-first workflows.

Yes. This Skill is designed specifically for TypeScript projects using Vitest for testing and Biome for code quality. The templates conform to these tools and enforce strict TypeScript usage alongside YAGNI principles and ADR/Design Doc workflows.

Yes. By defining shared project configuration, technology stack choices, and implementation principles upfront, project-context creates consistency across new TypeScript projects. This reduces setup time and ensures each project follows the same quality-first culture and architectural decisions.

Manual setup requires configuring project nature, tech stack, and principles for each project separately, consuming time and introducing inconsistency. Project-context templates automate this by providing pre-configured starting points aligned with LLM-driven implementation, Vitest testing, and Biome practices, reducing setup friction.

While project-context includes ADR/Design Doc workflows in its conformance model, the Skill guides you through customization. Basic understanding of your project's architecture and technology preferences is helpful, but the templates provide structure for teams new to these practices.