search-first

Solid

Research-before-building workflow. Use when adding new behavior, dependencies, or integrations to avoid reinventing and to stay compatible across codex/claude/gemini/opencode.

AI & Automation 52 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
57
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Search First ## Trigger Use this skill before you: - Add a new feature or workflow step - Introduce a new dependency, MCP server, or CLI integration - Write a new utility/helper that might already exist - Copy patterns from another repo (porting) ## Outcome Pick one of: **Adopt**, **Extend**, **Compose**, **Build**, with a short justification and evidence. ## Workflow (Fast) 1. **Define the need** - What is the smallest outcome that solves the problem? - Constraints: platform (macOS/Linux/Windows), clients (codex/claude/gemini/opencode), offline needs, security posture. 2. **Search locally (before the internet)** - CRG (if codemap installed): `semantic_search_nodes(query="<keyword>")` then `query_graph(pattern="callers_of"|"callees_of"|"tests_for", target="<name>")` — returns structural context that text search cannot provide - Code: `rg -n "<keyword>"` in the repo (fallback when CRG doesn't cover what you need) - Scripts: check `scripts/` for existing lifecycle/doctor commands. - Docs: check `README*` and `docs/`. 3. **Search existing skills** - Repo-local: `.codex/skills`, `.claude/skills`, `.agents/skills`. - Global: `~/.codex/skills`, `~/.claude/skills`, `~/.gemini/skills`, `~/.config/opencode/skills`. - Prefer reusing an existing skill name over creating a near-duplicate. 4. **Search the ecosystem (when needed)** - Prefer official docs and primary sources (project docs, RFCs, standards). - Prefer maintained, well-scoped libraries ...

Details

Author
rexleimo
Repository
rexleimo/aios
Created
6 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

search-first

Search npm / PyPI / MCP / GitHub / existing skills before writing code for any new feature, integration, library selection, or utility. Use whenever the user says 'add X functionality', 'implement Y', 'set up Z', 'integrate W', asks 'what library should I use for...', 'is there a package/client/MCP for...', proposes a specific tool while open to alternatives, or hits the planning.md wiring that routes dependency additions and self-built utilities here first. Especially when the task adds a dependency, picks between tools, or builds a utility that likely already exists (parser, checker, converter, linter, CI step, E2E framework, payment / auth / API client). DO NOT use for bug fixes, refactoring, config value edits, file summarization, or throwaway scripts whose approach the user already fully specified.

1 Updated 1 weeks ago
shimo4228
AI & Automation Listed

search-first

Search npm / PyPI / MCP / GitHub / existing skills before writing code for any new feature, integration, library selection, or utility. Use whenever the user says 'add X functionality', 'implement Y', 'set up Z', 'integrate W', asks 'what library should I use for...', 'is there a package/client/MCP for...', proposes a specific tool while open to alternatives, or hits the planning.md wiring that routes dependency additions and self-built utilities here first. Especially when the task adds a dependency, picks between tools, or builds a utility that likely already exists (parser, checker, converter, linter, CI step, E2E framework, payment / auth / API client). DO NOT use for bug fixes, refactoring, config value edits, file summarization, or throwaway scripts whose approach the user already fully specified.

2 Updated 3 weeks ago
shimo4228