Files
3a36fe8eaa feat(web): implement feature architecture standard with walletconnect migration (#6936)
* chore: setup spec-kit

* chore: add feature-architecture specs

* feat(web): implement feature architecture standard with walletconnect migration

- Add ESLint no-restricted-imports rule to enforce feature boundaries
- Create feature architecture documentation at apps/web/docs/feature-architecture.md
- Migrate walletconnect feature as reference implementation:
  - Add public API barrel file (index.ts) with lazy-loaded default export
  - Extract types to types.ts
  - Create feature flag hook (useIsWalletConnectEnabled)
  - Reorganize store into store/ directory
  - Move WalletConnectContext to components/WalletConnectContext/
  - Update all internal imports to relative paths
  - Update all external imports to use public API
- Fix affected test files (Header, useSafeWalletProvider)
- Update AGENTS.md with feature architecture reference

* fix prettier

---------

Co-authored-by: katspaugh <[email protected]>

Co-authored-by: Hanzo Dev <[email protected]>
2026-01-13 17:10:26 +01:00

1.1 KiB

description, tools
description tools
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
github/github-mcp-server/issue_write

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

  1. Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
  2. From the executed script, extract the path to tasks.
  3. Get the Git remote by running:
git config --get remote.origin.url

Caution

ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL

  1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.

Caution

UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL