Awesome-omni-skill search-web-implementation

Search the web monorepo (../app) to find how web handles equivalent functionality. Use when implementing mobile features that need to match web behavior, finding web routes, or understanding how web handles a specific feature like statements, portfolios, or user flows.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/search-web-implementation" ~/.claude/skills/diegosouzapw-awesome-omni-skill-search-web-implementation-6c8088 && rm -rf "$T"

manifest: skills/development/search-web-implementation/SKILL.md

source content

Search Web Implementation

Find how the web app handles equivalent functionality to ensure mobile/web consistency.

Web Monorepo Location

The web monorepo is located at

../app

relative to the mobile-app workspace, or at the absolute path

/Users/timmy.garrabrant/Developer/app

Key Directories

Directory	Contents
`client/`	Frontend React/TypeScript code (.tsx, .jsx, .ts)
`app/`	Rails controllers, views, models
`engines/`	Rails engines (modular features)
`subsystems/`	Domain subsystems (business logic)
`config/`	Routes, configuration

Search Strategy

1. Find Routes

Search Rails routes for URL patterns:

# Search route definitions
rg "quarterly_statements|annual_reports" ../app/config/ ../app/engines/*/config/
rg "activity.report|activity-report" ../app/config/ ../app/engines/*/config/

2. Find Frontend Components

Search React components in

client/

rg "QuarterlyStatement|AnnualReport" ../app/client/ --type tsx --type ts
rg "statement.*url|getStatementUrl" ../app/client/ -i

3. Find Backend Logic

Search subsystems and engines:

rg "def quarterly_statement|quarterly_statements" ../app/subsystems/ ../app/engines/
rg "activity_report|ActivityReport" ../app/subsystems/ ../app/engines/

4. Find Savers Routes

For savers-specific implementations:

rg "/savers/" ../app/client/ --type ts --type tsx
rg "savers.*route|route.*savers" ../app/config/ -i

Common Search Patterns

Find Feature by Name

rg "<feature_name>" ../app/client/ ../app/subsystems/ ../app/engines/

Find URL/Route Definitions

rg "<url_pattern>" ../app/config/routes.rb ../app/engines/*/config/routes.rb

Find React Components

rg "<ComponentName>" ../app/client/ --type tsx

Find GraphQL Resolvers

rg "<resolver_name>" ../app/subsystems/*/lib/*/graphql/

Workflow

Identify the feature - What mobile feature needs web parity?
Search client/ - Find frontend implementation
Search routes - Find URL structure
Search subsystems/ - Find backend business logic
Compare patterns - Note differences and document findings

Output Format

When reporting findings, include:

## Web Implementation: [Feature Name]

### Routes

- URL pattern: `/path/to/feature`
- File: `config/routes.rb:123`

### Frontend

- Component: `client/path/to/Component.tsx`
- Key logic: [brief description]

### Backend

- Subsystem: `subsystems/feature_name/`
- Key files: [list relevant files]

### Mobile Recommendation

[What the mobile app should do to match web]