Implement Small Feature

# Implement Small Feature

## Recipe

- Category: Implementation
- Recommended mode: Agent Mode
- Risk level: Low to Medium
- Estimated scope: Small

## Purpose

Implement one narrowly scoped feature in an existing Lovable project with minimal surface area.

This recipe is designed for changes that should fit into one focused implementation pass. It emphasizes execution discipline: inspect first, change only what is required, preserve existing contracts, verify the result, and stop when the accepted scope is complete.

## Use When

- the feature is already defined
- acceptance criteria are available
- the affected area is limited and understood
- the change should fit into a small number of files
- no major migration, provider change, or architecture redesign is required
- implementation can be verified in one pass

## Do Not Use When

- the feature is still ambiguous
- multiple unrelated outcomes are bundled together
- the change requires a broad refactor
- the database model or authorization model is still undecided
- a risky migration or rollout sequence is required
- the main task is debugging rather than implementation
- the feature should first be broken into multiple steps

## Inputs

- `[FEATURE]`: Small feature to implement
- `[USER_OUTCOME]`: Observable result for the user
- `[CURRENT_BEHAVIOR]`: Existing behavior
- `[DESIRED_BEHAVIOR]`: Required behavior
- `[ENTRY_POINT]`: Route, page, component, or trigger
- `[ACCEPTANCE_CRITERIA]`: Agreed pass/fail conditions
- `[RELEVANT_AREAS]`: Known files, components, services, routes, or data
- `[PERMISSIONS]`: Roles, ownership, tenant, or visibility rules
- `[CONSTRAINTS]`: Technical, design, compatibility, or product limits
- `[OUT_OF_SCOPE]`: Explicit exclusions
- `[VERIFICATION]`: Required checks or user flows

## Prompt