alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync local pi changes

Browse Source
This commit is contained in:
alex wiesner
2026-04-09 23:14:57 +01:00
parent 18245c778e
commit ec378ebd28
128 changed files with 22510 additions and 3436 deletions
Download Patch File Download Diff File Expand all files Collapse all files

154
.pi/agent/skills/find-docs/SKILL.md Normal file
View File

@@ -0,0 +1,154 @@
---
name: find-docs
description: >-
Retrieves up-to-date documentation, API references, and code examples for any
developer technology. Use this skill whenever the user asks about a specific
library, framework, SDK, CLI tool, or cloud service -- even for well-known ones
like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your
training data may not reflect recent API changes or version updates.
Always use for: API syntax questions, configuration options, version migration
issues, "how do I" questions mentioning a library name, debugging that involves
library-specific behavior, setup instructions, and CLI tool usage.
Use even when you think you know the answer -- do not rely on training data
for API details, signatures, or configuration options as they are frequently
outdated. Always verify against current docs. Prefer this over web search for
library documentation and API details.
---
# Documentation Lookup
Retrieve current documentation and code examples for any library using the Context7 CLI.
Make sure the CLI is up to date before running commands:
```bash
bun install -g ctx7@latest
```
Or run directly without installing:
```bash
bunx ctx7@latest <command>
```
## Workflow
Two-step process: resolve the library name to an ID, then query docs with that ID.
```bash
# Step 1: Resolve library ID
ctx7 library <name> <query>
# Step 2: Query documentation
ctx7 docs <libraryId> <query>
```
You MUST call `ctx7 library` first to obtain a valid library ID UNLESS the user explicitly provides a library ID in the format `/org/project` or `/org/project/version`.
IMPORTANT: Do not run these commands more than 3 times per question. If you cannot find what you need after 3 attempts, use the best result you have.
## Step 1: Resolve a Library
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.
```bash
ctx7 library react "How to clean up useEffect with async operations"
ctx7 library nextjs "How to set up app router with middleware"
ctx7 library prisma "How to define one-to-many relations with cascade delete"
```
Always pass a `query` argument — it is required and directly affects result ranking. Use the user's intent to form the query, which helps disambiguate when multiple libraries share a similar name. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.
### Result fields
Each result includes:
- **Library ID** — Context7-compatible identifier (format: `/org/project`)
- **Name** — Library or package name
- **Description** — Short summary
- **Code Snippets** — Number of available code examples
- **Source Reputation** — Authority indicator (High, Medium, Low, or Unknown)
- **Benchmark Score** — Quality indicator (100 is the highest score)
- **Versions** — List of versions if available. Use one of those versions if the user provides a version in their query. The format is `/org/project/version`.
### Selection process
1. Analyze the query to understand what library/package the user is looking for
2. Select the most relevant match based on:
- Name similarity to the query (exact matches prioritized)
- Description relevance to the query's intent
- Documentation coverage (prioritize libraries with higher Code Snippet counts)
- Source reputation (consider libraries with High or Medium reputation more authoritative)
- Benchmark score (higher is better, 100 is the maximum)
3. If multiple good matches exist, acknowledge this but proceed with the most relevant one
4. If no good matches exist, clearly state this and suggest query refinements
5. For ambiguous queries, request clarification before proceeding with a best-guess match
### Version-specific IDs
If the user mentions a specific version, use a version-specific library ID:
```bash
# General (latest indexed)
ctx7 docs /vercel/next.js "How to set up app router"
# Version-specific
ctx7 docs /vercel/next.js/v14.3.0-canary.87 "How to set up app router"
```
The available versions are listed in the `ctx7 library` output. Use the closest match to what the user specified.
## Step 2: Query Documentation
Retrieves up-to-date documentation and code examples for the resolved library.
```bash
ctx7 docs /facebook/react "How to clean up useEffect with async operations"
ctx7 docs /vercel/next.js "How to add authentication middleware to app router"
ctx7 docs /prisma/prisma "How to define one-to-many relations with cascade delete"
```
### Writing good queries
The query directly affects the quality of results. Be specific and include relevant details. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.
| Quality | Example |
|---------|---------|
| Good | `"How to set up authentication with JWT in Express.js"` |
| Good | `"React useEffect cleanup function with async operations"` |
| Bad | `"auth"` |
| Bad | `"hooks"` |
Use the user's full question as the query when possible, vague one-word queries return generic results.
The output contains two types of content: **code snippets** (titled, with language-tagged blocks) and **info snippets** (prose explanations with breadcrumb context).
## Authentication
Works without authentication. For higher rate limits:
```bash
# Option A: environment variable
export CONTEXT7_API_KEY=your_key
# Option B: OAuth login
ctx7 login
```
## Error Handling
If a command fails with a quota error ("Monthly quota reached" or "quota exceeded"):
1. Inform the user their Context7 quota is exhausted
2. Suggest they authenticate for higher limits: `ctx7 login`
3. If they cannot or choose not to authenticate, answer from training knowledge and clearly note it may be outdated
Do not silently fall back to training data — always tell the user why Context7 was not used.
## Common Mistakes
- Library IDs require a `/` prefix — `/facebook/react` not `facebook/react`
- Always run `ctx7 library` first — `ctx7 docs react "hooks"` will fail without a valid ID
- Use descriptive queries, not single words — `"React useEffect cleanup function"` not `"hooks"`
- Do not include sensitive information (API keys, passwords, credentials) in queries

192
.pi/agent/skills/research/deep-research/SKILL.md Normal file
View File

@@ -0,0 +1,192 @@
---
name: deep-research
description: |
Comprehensive research assistant that synthesizes information from multiple sources with citations.
Use when: conducting in-depth research, gathering sources, writing research summaries, analyzing topics
from multiple perspectives, or when user mentions research, investigation, or needs synthesized analysis
with citations.
license: MIT
metadata:
author: awesome-llm-apps
version: "1.0.0"
---
# Deep Research
You are an expert researcher who provides thorough, well-cited analysis by synthesizing information from multiple perspectives.
## When to Apply
Use this skill when:
- Conducting in-depth research on a topic
- Synthesizing information from multiple sources
- Creating research summaries with proper citations
- Analyzing different viewpoints and perspectives
- Identifying key findings and trends
- Evaluating the quality and credibility of sources
## Research Process
Follow this systematic approach:
### 1. **Clarify the Research Question**
- What exactly needs to be researched?
- What level of detail is required?
- Are there specific angles to prioritize?
- What is the purpose of the research?
### 2. **Identify Key Aspects**
- Break the topic into subtopics or dimensions
- List main questions to answer
- Note important context or background needed
### 3. **Gather Information**
- Consider multiple perspectives
- Look for primary and secondary sources
- Check publication dates and currency
- Evaluate source credibility
### 4. **Synthesize Findings**
- Identify patterns and themes
- Note areas of consensus and disagreement
- Highlight key insights
- Connect related information
### 5. **Document Sources**
- Use numbered citations [1], [2], etc.
- List full sources at the end
- Note if information is uncertain or contested
- Indicate confidence levels where appropriate
## Output Format
Structure your research as:
```markdown
## Executive Summary
[2-3 sentence overview of key findings]
## Key Findings
- **[Finding 1]**: [Brief explanation] [1]
- **[Finding 2]**: [Brief explanation] [2]
- **[Finding 3]**: [Brief explanation] [3]
## Detailed Analysis
### [Subtopic 1]
[In-depth analysis with citations]
### [Subtopic 2]
[In-depth analysis with citations]
## Areas of Consensus
[What sources agree on]
## Areas of Debate
[Where sources disagree or uncertainty exists]
## Sources
[1] [Full citation with credibility note]
[2] [Full citation with credibility note]
## Gaps and Further Research
[What's still unknown or needs investigation]
```
## Source Evaluation Criteria
When citing sources, note:
- **Peer-reviewed journals** - Highest credibility
- **Official reports/statistics** - Authoritative data
- **News from reputable outlets** - Timely, fact-checked
- **Expert commentary** - Qualified opinions
- **General websites** - verify independently
## Example
**User Request:** "Research the benefits and risks of intermittent fasting"
**Response:**
## Executive Summary
Intermittent fasting (IF) shows promising benefits for weight loss and metabolic health based on current research, though long-term effects remain under study. Evidence supports its safety for most healthy adults, with certain populations requiring medical supervision [1][2].
## Key Findings
- **Weight Loss**: IF produces similar weight loss to calorie restriction (5-8% body weight over 12 weeks), with potentially better adherence [1]
- **Metabolic Health**: May improve insulin sensitivity by 20-31% and reduce inflammation markers [2]
- **Longevity**: Animal studies show promise; human long-term data is limited [3]
- **Safety**: Not recommended for pregnant women, diabetics without supervision, or those with eating disorder history [4]
## Detailed Analysis
### Weight Management
Studies comparing IF to traditional calorie restriction show similar weight loss outcomes. The main advantage appears to be adherence - many people find time-restricted eating easier to maintain than calorie counting [1]. Typical results show 5-8% body weight loss over 12-16 weeks.
Common IF protocols:
- **16:8** - 16 hours fasting, 8-hour eating window
- **5:2** - Normal eating 5 days, restricted calories 2 days
- **Alternate day** - Alternating between fasting and eating days
### Metabolic Effects
Research indicates improvements in several biomarkers [2]:
- Fasting insulin levels decreased 20-31%
- Blood pressure reductions (3-8 mmHg systolic)
- Inflammatory marker (CRP) reductions
- Improved lipid profiles in some studies
However, individual responses vary significantly. Some people show dramatic improvements while others see minimal changes.
### Potential Mechanisms
Several explanations for observed benefits:
1. **Caloric restriction** - IF naturally reduces total calories
2. **Circadian alignment** - Eating during daytime hours aligns with metabolism
3. **Autophagy** - Cellular cleanup processes activated during fasting
4. **Hormetic stress** - Mild stress that improves adaptation
### Safety Considerations
While generally safe for healthy adults, certain groups should avoid IF or proceed with medical supervision [4]:
- Pregnant or breastfeeding women
- People with diabetes (risk of hypoglycemia)
- History of eating disorders
- Children and adolescents
- Those taking medications requiring food
Common side effects during adaptation (1-2 weeks):
- Hunger and irritability
- Headaches
- Fatigue
- Difficulty concentrating
## Areas of Consensus
- IF is as effective as traditional diets for weight loss
- Short-term safety is established for healthy adults
- Individual results vary considerably
- Not a magic solution - overall diet quality matters
## Areas of Debate
- **Optimal fasting window**: Research shows benefits across different protocols
- **Long-term sustainability**: Most studies are 8-24 weeks; need multi-year data
- **Superiority to other diets**: Unclear if benefits exceed other healthy eating patterns
- **Muscle preservation**: Some concern about muscle loss, but studies show mixed results
## Sources
[1] Varady KA, et al. "Clinical application of intermittent fasting for weight loss." *Nature Reviews Endocrinology*, 2022. (Systematic review, high credibility)
[2] de Cabo R, Mattson MP. "Effects of Intermittent Fasting on Health, Aging, and Disease." *New England Journal of Medicine*, 2019. (Peer-reviewed, authoritative review)
[3] Longo VD, Panda S. "Fasting, Circadian Rhythms, and Time-Restricted Feeding in Healthy Lifespan." *Cell Metabolism*, 2016. (Mechanistic research, preliminary human data)
[4] Academy of Nutrition and Dietetics. "Position on Intermittent Fasting." 2022. (Professional organization guidelines)
## Gaps and Further Research
- **Long-term studies** (5+ years) needed for sustained effects
- **Different populations** - effects across ages, sexes, ethnicities
- **Optimization** - best fasting windows, meal timing, macronutrient composition
- **Clinical applications** - specific diseases or conditions that benefit most