project-feature

Adds a new field to the Project entity across schema, validation, and UI.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/jhlee0409/sidedish --skill project-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-feature
Source: https://github.com/jhlee0409/sidedish/tree/main/.claude/skills/project-feature
Command: npx skills add https://github.com/jhlee0409/sidedish --skill project-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you safely extend the Project data model by adding new fields, updating type definitions, API routes, forms, and displays, without breaking existing functionality.

Core Features & Use Cases

  • End-to-end field addition: add new fields to frontend types, Firestore documents, and API contracts.
  • Synchronized updates: propagate schema changes through validation rules, forms, and UI components.
  • Real-world example: when you need a new category field on Projects, this Skill coordinates type, API, and UI changes in one workflow.

Quick Start

Add a new field named category to a sample Project and update types, API routes, forms, and the project card display.

Frequently Asked Questions about project-feature

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

FAQPage Schema
How do I add a new field to my Project schema across frontend and backend?

Add a new field to your Project schema by updating frontend types, Firestore documents, API routes, and validation logic in a single coordinated workflow. This Skill walks through synchronizing type definitions, API contracts, form inputs, and UI components to ensure the new field flows consistently through your entire stack without breaking existing data.

Can I extend Project validation and forms when adding new fields?

Yes. When adding a field, this Skill covers updating validation rules alongside schema changes, so new fields are validated on both backend and frontend. It includes updating form components and display logic to render the new field correctly in your UI.

How do I keep Project type definitions synchronized across frontend and backend?

Type-safety is maintained by propagating schema changes through both frontend types and Firestore API responses simultaneously. This Skill ensures frontend types, backend validation, and API contracts stay in sync, reducing type mismatches and runtime errors.

What's the best way to add Project fields without breaking existing functionality?

This Skill implements backward-compatible migrations when extending the Project model, so new fields don't disrupt current data or API consumers. It coordinates schema updates, validation, and UI rendering while preserving existing workflows.

Do I need to update both API routes and forms when adding a Project field?

Yes. Adding a Project field requires updating CRUD API routes to handle the new data and modifying form components to accept and display it. This Skill covers both changes as part of the end-to-end field addition process.

How does this handle frontend and backend schema consistency for new Project fields?

The Skill ensures consistent data flow by updating type definitions on both sides simultaneously and validating new fields through security checks. This prevents schema drift and maintains data integrity between your frontend, API, and Firestore backend.