new-feature

Coordinate Django backend, React UI, and agent wiring for new features without duplicating business logic.

Updated Sep 21, 2025
One-click install
npx skills add https://github.com/jammindev/house --skill new-feature-jammindev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-feature
Source: https://github.com/jammindev/house/tree/main/.claude/skills/new-feature
Command: npx skills add https://github.com/jammindev/house --skill new-feature-jammindev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement a new feature, module, or business entity in the house repository without duplicating logic across the Django API, the conversational agent, and the React UI.

Core Features & Use Cases

  • Backend implementation: Define models, serializers, services, views, URLs, admin registration, and migrations for a new app or an extension of an existing one.
  • Agent wiring: Register searchable, listable, and writable entities so the agent can discover, list, create, and update them through shared service logic.
  • Frontend integration: Add a single API client, React Query hooks, feature pages, dialogs, cards, routing, sidebar entries, and anchored entity assistants.
  • Production-ready workflow: Follow the project’s pattern for validation, undo support, tests, documentation, and delivery for a complete end-to-end feature.

Quick Start

Use the new-feature skill to implement the next feature in this repository by following the existing product backlog and the shared backend, agent, and UI patterns.

Frequently Asked Questions about new-feature

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

FAQPage Schema
How do I implement a new Django feature without duplicating business logic across the API, agent, and React UI?

To implement a Django feature without duplication, coordinate backend models, agent capability wiring, and React UI integration through a shared service layer. This ensures REST APIs, agent tools, and frontend views stay consistent across multi-step product changes.

How does agent wiring work when adding a new entity to a Django and React application?

Agent wiring registers searchable, listable, and writable entities so the conversational agent can discover, list, create, and update them. The agent interacts with new entities through shared service-layer logic rather than duplicated code.

What is the best way to structure a React frontend integration for a new Django backend module?

The best way to structure React frontend integration is using a single UI API client with React Query hooks. Add feature pages, dialogs, routing, and sidebar entries to maintain consistency with the backend service layer and agent tools.

Can I use this approach to extend an existing Django app instead of creating a new one?

Yes, you can extend an existing Django app. Define serializers, services, views, and migrations for the extension, then wire the new capabilities to the agent and React UI using the same shared service-layer pattern.

What do I need to ship a production-ready feature across Django, agent tools, and React views?

To ship a production-ready feature, follow the project pattern for validation, undo support, tests, and documentation. Ensure shared service-layer writes, agent registry declarations, and a single UI API client are fully implemented.

Why does my new entity module require changes across REST APIs, agent tools, and frontend views simultaneously?

Your entity module requires simultaneous changes because scoped household features must stay consistent across REST APIs, agent tools, and frontend views. A shared service layer prevents duplicated business logic during multi-step product changes.