Feature Context

Load repo rules, coding standards, and domain feature references before future feature work. Use when adding, changing, reviewing, or planning behavior in this codebase and the task mentions a feature, route, product area, component, service, hook, checkout, auth, onboarding, community, admin, feed, Figma UI, or shared utility.

Source: .agents/skills/feature-context/SKILL.md

Metadata

• name: feature-context

Content

Feature Context

Use this skill to gather durable project context before feature work. It is a context-loading workflow, not a replacement for reading the current code.

Goal

Start every feature task with:

1. Mandatory repo rules from .agents/rules/*.mdc.
2. Relevant coding standards from .agents/references/coding-standard/.
3. Relevant domain pack(s) from .agents/references/features/.
4. Live inspection of the actual files that will be changed.

Required Workflow

1. Load repo rules

   • Read AGENTS.md.
   • Read all files in .agents/rules/.
   • If a rule links to a coding standard, load that standard too.

2. Classify the task

   • Use user wording, routes, file paths, service names, component names, and code search results.
   • Load every matching feature reference listed below.
   • If the task spans multiple domains, load all of them.

3. Inspect live code

   • Search first with rtk rg or rtk find when RTK is available.
   • If RTK is unavailable, use plain rg or find with the same query. RTK is optional command-output compression and must not block live code inspection.
   • Read the actual route/component/hook/service files before planning or editing.
   • Prefer existing local patterns over generic advice from the reference docs.

4. Use the feature template for new domains

   • If no domain pack fits and the task introduces a durable product area, create or update a feature reference using .agents/references/features/_template.md.
   • Keep references as context. Do not put implementation details there that only apply to one temporary branch unless they describe a durable convention or gotcha.

5. After substantial work

   • If a change adds, removes, or renames a route, service, hook, major component, API contract, redirect, or recurring domain gotcha, update the relevant feature reference in the same change.
   • Run bun run sync-agents after editing .agents/.

Domain Selection

Load these references when the task matches the listed terms or paths:

Reference	Match when task mentions or touches
.agents/references/features/community-public-pages.md	src/pages/[communityLink], community home/profile, public community pages, product cards on community pages, public/member CTAs, public SEO pages
.agents/references/features/checkout-and-payments.md	checkout, payment, Stripe, PayPal, Ebanx, discount, fee, pricing, 3DS, payment authentication, abandoned checkout, physical product checkout
.agents/references/features/products-and-commerce.md	products, courses, events, challenges, memberships, digital files, forms, sessions, physical products, unified product cards, product detail pages
.agents/references/features/onboarding-and-setup.md	get-started, onboarding, creator setup, business setup, plan selection, signup modal, referral code, base currency, social media setup
.agents/references/features/auth-routing-and-middleware.md	auth, login, logout, OAuth, reset password, middleware, redirects, locale/country routing, portal paths, webview/Flutter routing
.agents/references/features/creator-admin-and-pro.md	creator/admin/pro surfaces, KYC, revenue, plans, pro subscription, lead forms, announcements management, integrations, creator tools
.agents/references/features/engagement-feed-chat-and-announcements.md	feed, comments, reactions, announcements, activity feed, chat, messages, member details, sessions/calendar engagement
.agents/references/features/shared-services-hooks-and-utilities.md	shared hooks, service helpers, request helpers, analytics, storage wrappers, uploads, Sentry/PostHog, date/time, localization, route utilities

Coding Standard Selection

• Figma/design implementation: load .agents/references/coding-standard/figma-guidance.md.
• Any task that touches React/Next/TS/TSX in src/ (components, pages, hooks, data fetching, imports, bundles): load .agents/references/coding-standard/vercel-react-best-practices/REPO-GUIDANCE.md and the relevant detailed files under .agents/references/coding-standard/vercel-react-best-practices/rules/ for the specific concern (waterfalls, bundle, rerender, rendering, etc.).
• React hooks/effects/state derivation: load .agents/references/coding-standard/useeffect-guidance.md.
• New pages, page refactors, shared components, services, utilities, or large feature work: load .agents/references/coding-standard/page-structure.md.
• For all React/TypeScript work, also load the matching .agents/rules/*.mdc files.

Output Expectations

When using this skill, state the context loaded before acting:

Context loaded:
- Rules: <rule files>
- Coding standards: <standard files or none>
- Feature references: <feature files>
- Live files inspected: <source files>

Then proceed with the task using the normal workflow for implementation, review, or planning.

For coordinated feature execution across subagents/worktrees, load .agents/skills/implement-feature/SKILL.md after this context pass. feature-context tells agents what domain context to load; implement-feature controls requirement clarification, checklist creation, worktree assignment, QA, code review, and integration.

Non-Goals

• Do not skip code search because a reference exists.
• Do not create a feature reference for a one-off bug unless it reveals durable domain context.
• Do not duplicate .agents/rules content inside feature references; link to rules instead.
• Do not commit or push unless the user explicitly asks.