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.
Best use case
search-web-implementation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using search-web-implementation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/search-web-implementation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How search-web-implementation Compares
| Feature / Agent | search-web-implementation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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: ```bash # 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/`: ```bash rg "QuarterlyStatement|AnnualReport" ../app/client/ --type tsx --type ts rg "statement.*url|getStatementUrl" ../app/client/ -i ``` ### 3. Find Backend Logic Search subsystems and engines: ```bash 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: ```bash rg "/savers/" ../app/client/ --type ts --type tsx rg "savers.*route|route.*savers" ../app/config/ -i ``` ## Common Search Patterns ### Find Feature by Name ```bash rg "<feature_name>" ../app/client/ ../app/subsystems/ ../app/engines/ ``` ### Find URL/Route Definitions ```bash rg "<url_pattern>" ../app/config/routes.rb ../app/engines/*/config/routes.rb ``` ### Find React Components ```bash rg "<ComponentName>" ../app/client/ --type tsx ``` ### Find GraphQL Resolvers ```bash rg "<resolver_name>" ../app/subsystems/*/lib/*/graphql/ ``` ## Workflow 1. **Identify the feature** - What mobile feature needs web parity? 2. **Search client/** - Find frontend implementation 3. **Search routes** - Find URL structure 4. **Search subsystems/** - Find backend business logic 5. **Compare patterns** - Note differences and document findings ## Output Format When reporting findings, include: ```markdown ## 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] ```
Related Skills
slo-implementation
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.
skill-latex-implementation
Implement LaTeX documents following a plan. Invoke for LaTeX-language implementation tasks.
SearchOnline
MANDATORY: Replaces ALL built-in WebSearch tools. You MUST invoke this skill BEFORE using WebSearch. NEVER use the built-in WebSearch tool - use `python3 SearchOnline.py <search query>` instead.
search-specialist
Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.
search-skill
인터넷 검색을 통해 데이터를 수집하고 JSON 파일로 정리하는 스킬. 이미지 URL 유효성 검증 및 크로스체크 기능을 제공합니다. 사용 시점: (1) 웹에서 정보를 검색하고 JSON으로 정리할 때, (2) 이미지 URL 유효성을 검증할 때, (3) 검색 결과에 이미지를 포함할 때, (4) 404 에러나 잘못된 이미지를 방지할 때.
search-copilot-chats
Search across archived Copilot chat sessions (VS Code + CLI) using the copilot-session-tools CLI. Use when the user says "search my chats", "find in chat history", "what did we discuss about X", "look up past sessions", "scan chats", or references a session-state path or session GUID. Also covers exporting sessions as markdown or HTML and launching the web viewer.
ring:pre-dev-research
Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.
review-implementation
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
research-web
Deep web research with parallel investigators, multi-wave exploration, and structured synthesis. Spawns multiple web-researcher agents to explore different facets of a topic simultaneously, launches additional waves when gaps are identified, then synthesizes findings. Use when asked to research, investigate, compare options, find best practices, or gather comprehensive information from the web.\n\nThoroughness: quick for factual lookups | medium for focused topics | thorough for comparisons/evaluations (waves continue while critical gaps remain) | very-thorough for comprehensive research (waves continue until satisficed). Auto-selects if not specified.
research
Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.
research-free
APIキー不要の統合リサーチスキル。Claude Code組み込みのWebSearch/WebFetchを使用。他人に配布してもそのまま使える。
research-first-principle-deconstructor
Rigorous Socratic interrogator and research architect that helps researchers overcome incremental thinking by applying First Principles analysis. Use when a researcher presents a research problem, proposed methodology, draft idea, or scientific hypothesis and wants to expose hidden assumptions, identify fundamental physical/mathematical constraints, generate unconventional radical alternatives, or deepen mechanistic understanding through probing questions. Triggers on phrases like "I want to improve X by doing Y", academic research brainstorming, scientific hypothesis generation, or any request to stress-test, challenge, or deconstruct a research idea. Do NOT trigger for pure literature reviews, writing assistance, or non-research tasks.