development

Enforce design-first development with type-driven contracts and automated checks.

18|Updated Apr 5, 2021
One-click install
npx skills add https://github.com/inocan-group/inferred-types --skill development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development
Source: https://github.com/inocan-group/inferred-types/tree/main/.claude/skills/development
Command: npx skills add https://github.com/inocan-group/inferred-types --skill development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the enforcement of strict code quality standards and development practices, preventing technical debt and ensuring all work is complete and thoroughly tested before commitment. It eliminates the common pitfalls of "TODO" markers and incomplete implementations.

Core Features & Use Cases

  • TODO Marker Enforcement: Automatically flags and blocks commits with TODO, FIXME, XXX, or HACK markers, ensuring immediate resolution of incomplete work.
  • Type-Driven Development Guidance: Provides a structured workflow for designing and implementing type utilities and runtime functions, emphasizing complete solutions and comprehensive testing.
  • Technical Debt Prevention: Guides developers to address issues immediately, promoting a culture of "completeness over speed" and "design before code."

Quick Start

Analyze the current codebase for any outstanding TODO markers and provide a detailed plan to resolve them according to the development skill's guidelines.

Frequently Asked Questions about development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent TODO and FIXME markers from being committed to my repository?

This Skill automatically flags and blocks commits containing TODO, FIXME, XXX, or HACK markers, enforcing immediate resolution of incomplete work before code reaches the repository. It integrates with CI pipelines to reject stubs and ensure all work is complete.

What's the best way to enforce code quality standards across a TypeScript codebase?

Enforce design-first development by requiring design documentation before implementation, mandating strong typing as code contracts, and automating checks to reject incomplete work. This approach prevents technical debt and ensures comprehensive testing across feature work, refactoring, and code reviews.

How can I eliminate technical debt in development workflows?

Address issues immediately through automated enforcement of complete implementations, type-driven development practices, and upfront design documentation. This promotes a culture of completeness over speed, resolving debt at the point of creation rather than accumulating it.

Can I use this for onboarding and code review processes?

Yes. This Skill applies to feature work, refactoring, code reviews, onboarding, and CI pipelines, ensuring all developers follow strict code quality standards and design-first practices from the start, reducing incomplete implementations across the team.

Does this enforce type safety in TypeScript projects?

Yes. Type-driven development guidance emphasizes designing type utilities and runtime functions with strong typing as the code interface, ensuring comprehensive solutions and complete testing through type contracts.

What happens if developers try to commit incomplete work?

Automated checks reject commits containing TODO markers or incomplete implementations, forcing immediate resolution before code reaches the repository. This prevents incomplete work from entering feature branches, refactoring efforts, or CI pipelines.