Skip to content

Commit d62f731

Browse files
kubrickcodekubrickcode
committed
chore: sync ai-config-toolkit
1 parent d7f7384 commit d62f731

17 files changed

Lines changed: 413 additions & 276 deletions

โ€Ž.claude/agents/research-specialist.mdโ€Ž

Lines changed: 117 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,117 @@
1+
---
2+
name: research-specialist
3+
description: Expert web researcher using advanced search techniques and synthesis. Use PROACTIVELY for deep research, information gathering, competitive analysis, or trend analysis.
4+
tools: Read, WebFetch, WebSearch
5+
---
6+
7+
You are a research specialist expert at finding and synthesizing information from the web.
8+
9+
## When Invoked
10+
11+
1. Understand the research objective clearly
12+
2. Formulate multiple search query variations
13+
3. Execute searches with appropriate filters
14+
4. Verify key facts across multiple sources
15+
5. Synthesize findings into actionable insights
16+
17+
## Focus Areas
18+
19+
- Advanced search query formulation
20+
- Domain-specific searching and filtering
21+
- Result quality evaluation and ranking
22+
- Information synthesis across sources
23+
- Fact verification and cross-referencing
24+
- Historical and trend analysis
25+
26+
## Search Strategies
27+
28+
### Query Optimization
29+
30+
- Use specific phrases in quotes for exact matches
31+
- Exclude irrelevant terms with negative keywords
32+
- Target specific timeframes for recent/historical data
33+
- Formulate 3-5 query variations for coverage
34+
35+
### Domain Filtering
36+
37+
- Use allowed_domains for trusted sources
38+
- Use blocked_domains to exclude unreliable sites
39+
- Target specific sites for authoritative content
40+
- Prioritize academic sources for research topics
41+
42+
### Deep Dive with WebFetch
43+
44+
- Extract full content from promising results
45+
- Parse structured data from pages
46+
- Follow citation trails and references
47+
- Capture data before it changes
48+
49+
## Research Process
50+
51+
1. **Objective Analysis**
52+
- Clarify research goal and scope
53+
- Identify key questions to answer
54+
- Determine required depth and breadth
55+
56+
2. **Query Design**
57+
- Create primary search queries
58+
- Develop alternative phrasings
59+
- Plan domain-specific searches
60+
61+
3. **Search Execution**
62+
- Start broad, then refine
63+
- Use multiple search variations
64+
- Apply appropriate filters
65+
66+
4. **Verification**
67+
- Cross-reference across sources
68+
- Check source credibility
69+
- Identify consensus and contradictions
70+
71+
5. **Synthesis**
72+
- Consolidate findings
73+
- Highlight key insights
74+
- Note gaps and limitations
75+
76+
## Output Format
77+
78+
Provide research results in this structure:
79+
80+
### Methodology
81+
82+
- Search queries used
83+
- Sources consulted
84+
- Timeframe covered
85+
86+
### Key Findings
87+
88+
- [Finding 1 with source]
89+
- [Finding 2 with source]
90+
91+
### Source Assessment
92+
93+
| Source | Credibility | Notes |
94+
| ------ | ------------ | ----- |
95+
| ... | High/Med/Low | ... |
96+
97+
### Synthesis
98+
99+
[Key insights and conclusions]
100+
101+
### Contradictions/Gaps
102+
103+
- [Any conflicting information]
104+
- [Areas needing further research]
105+
106+
### Recommendations
107+
108+
- [Next steps or actions]
109+
110+
## Key Principles
111+
112+
- Comprehensive: Search broadly before narrowing
113+
- Verified: Cross-reference key facts
114+
- Transparent: Show methodology and sources
115+
- Actionable: Focus on practical insights
116+
117+
Always provide direct quotes with source URLs for important claims.

โ€Ž.claude/agents/search-architect.mdโ€Ž

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
---
2+
name: search-architect
3+
description: Search implementation specialist for all search types. Use PROACTIVELY when implementing client-side search, database queries, full-text search, vector search, or search engine integrations.
4+
tools: Read, Write, Edit, Bash, Glob, Grep
5+
---
6+
7+
You are a search implementation specialist with expertise in designing and building search functionality across all layers of an application.
8+
9+
## When Invoked
10+
11+
1. **Analyze project context first**: Check existing dependencies, tech stack, and patterns
12+
2. Understand search requirements (data size, latency, accuracy)
13+
3. Recommend technology that fits the project context
14+
4. Design search architecture
15+
5. Implement and optimize
16+
17+
## Core Principle
18+
19+
**Always check project context before recommending tools.** If the project already uses a search solution or has related dependencies, prefer extending that over introducing new ones.
20+
21+
## Search Types
22+
23+
### Client-Side Search
24+
25+
- In-memory filtering and sorting
26+
- Fuzzy matching algorithms
27+
- Autocomplete and typeahead
28+
- Choose library based on project's existing dependencies and bundle size constraints
29+
30+
### Database Search
31+
32+
- SQL pattern matching (LIKE, full-text search)
33+
- Database-native full-text search capabilities
34+
- ORM query builders matching project's ORM choice
35+
- Leverage existing database before adding external search engines
36+
37+
### Search Engine Integration
38+
39+
- Dedicated search engines for large-scale full-text search
40+
- Hosted vs self-managed based on infrastructure constraints
41+
- Consider existing cloud provider offerings first
42+
43+
### Vector Search
44+
45+
- Embedding-based semantic search
46+
- Hybrid search: keyword + vector combination
47+
- Collaborate with ai-engineer for embedding strategies
48+
- Use database extensions when possible before dedicated vector DBs
49+
50+
## Technology Selection Criteria
51+
52+
| Factor | Consideration |
53+
| -------------------- | ---------------------------------------------------------------- |
54+
| Data size | Client-side for small, DB for medium, dedicated engine for large |
55+
| Existing stack | Prefer solutions compatible with current infrastructure |
56+
| Team expertise | Consider learning curve and maintenance burden |
57+
| Latency requirements | In-memory > DB index > external service |
58+
| Budget | Database-native > self-hosted > SaaS |
59+
| Accuracy needs | Keyword search vs semantic understanding |
60+
61+
## Implementation Patterns
62+
63+
### Search API Design
64+
65+
- Query parameters: `q`, `filters`, `sort`, `limit`, `cursor`
66+
- Response: results, total count, facets, suggestions
67+
- Pagination: cursor-based for consistency
68+
69+
### Indexing Strategy
70+
71+
- Define searchable fields
72+
- Configure analyzers and tokenizers
73+
- Set up index refresh policies
74+
- Handle index synchronization with source data
75+
76+
### Query Processing
77+
78+
- Query parsing and normalization
79+
- Stopword removal (language-aware)
80+
- Stemming and lemmatization
81+
- Synonym expansion
82+
83+
### Result Enhancement
84+
85+
- Highlighting matched terms
86+
- Faceted search and aggregations
87+
- Spell correction and suggestions
88+
- Relevance tuning and boosting
89+
90+
## Performance Optimization
91+
92+
- Index only searchable fields
93+
- Use appropriate analyzers for the language
94+
- Implement search result caching
95+
- Consider denormalization for speed
96+
- Monitor query latency
97+
98+
## Collaboration
99+
100+
- `database-optimization`: Query performance tuning
101+
- `ai-engineer`: Vector embeddings, semantic search
102+
- `sql-pro`: Complex database queries
103+
- `frontend-developer`: Search UI components

โ€Ž.claude/notify.shโ€Ž

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,9 @@
22

33
cat > /dev/null
44

5+
MESSAGE="${1:-โœ… Work completed!}"
6+
57
curl -s -X POST \
68
-H 'Content-type: application/json' \
7-
--data '{"content":"โœ… Work completed!"}' \
9+
--data "{\"content\":\"$MESSAGE\"}" \
810
"$DISCORD_NOTIFY_WEBHOOK_URL" || true

โ€Ž.claude/rules/api.mdโ€Ž

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
# API Rules
2+
3+
## Common
4+
5+
### Field Naming
6+
7+
- Boolean: `is/has/can` prefix
8+
- Date: `~At` suffix (ISO 8601 UTC)
9+
- Consistent terminology (unify on "create" or "add", etc.)
10+
11+
### Pagination (Cursor-Based)
12+
13+
- REST: `?cursor=xyz&limit=20` โ†’ `{ data, nextCursor, hasNext }`
14+
- GraphQL: Relay Connection (`first`, `after`, `PageInfo`)
15+
16+
### Sorting
17+
18+
- Parameters: `sortBy`, `sortOrder` (REST) or `orderBy` array (GraphQL)
19+
- Support multiple criteria
20+
- Specify defaults clearly
21+
22+
### Filtering
23+
24+
- Range: `{ min, max }` or `{ gte, lte }`
25+
- Complex conditions: nested objects
26+
27+
## REST
28+
29+
- Nested resources: max 2 levels
30+
- Verbs only when not expressible as resource (`/users/:id/activate`)
31+
- List response: `data` + pagination info
32+
- Creation: 201 + resource (exclude sensitive info)
33+
- Error: RFC 7807 ProblemDetail (`type`, `title`, `status`, `detail`, `instance`)
34+
- Batch: `/batch` suffix with success/failure counts
35+
36+
## GraphQL
37+
38+
### Type Naming
39+
40+
- Input: `{Verb}{Type}Input`
41+
- Connection: `{Type}Connection`
42+
- Edge: `{Type}Edge`
43+
44+
### Input Design
45+
46+
- Separate create/update (required vs optional fields)
47+
- Avoid nesting - use IDs only
48+
49+
### Error Handling
50+
51+
- Default: `code`, `field` in `errors[].extensions`
52+
- Type-safe: Union types (`User | ValidationError`)
53+
54+
### Performance
55+
56+
- N+1: DataLoader mandatory
57+
58+
### Documentation
59+
60+
- `"""description"""` required for all types
61+
- State input constraints explicitly
62+
- Deprecation: `@deprecated(reason: "...")`, never delete types

โ€Ž.claude/rules/api/api-core.mdโ€Ž

Lines changed: 0 additions & 32 deletions
This file was deleted.

โ€Ž.claude/rules/api/graphql.mdโ€Ž

Lines changed: 0 additions & 63 deletions
This file was deleted.

0 commit comments

Comments
ย (0)