Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
Generates troubleshooting guides and FAQ sections for PHP projects. Creates problem-solution documentation.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Generate helpful troubleshooting guides and FAQ documentation.
# Troubleshooting
## Quick Fixes
{common issues with quick solutions}
## Installation Issues
{installation problems}
## Configuration Issues
{config problems}
## Runtime Errors
{errors during execution}
## FAQ
{frequently asked questions}
## Getting Help
{how to report issues}
## Quick Fixes
### Reset to Known Good State
```bash
# Clear cache
rm -rf var/cache/*
# Reinstall dependencies
rm -rf vendor/ composer.lock
composer install
# Verify installation
php vendor/bin/package verify
| Symptom | Quick Fix |
|---|---|
| "Class not found" | Run composer dump-autoload |
| Permission denied | Run chmod -R 755 var/ |
| Config not loading | Check .env file exists |
| Connection refused | Verify service is running |
### Installation Issues Section
```markdown
## Installation Issues
### Composer Install Fails
**Symptom:**
Your requirements could not be resolved to an installable set of packages.
**Solutions:**
1. **Update Composer:**
```bash
composer self-update
Clear Composer cache:
composer clear-cache
Check PHP version:
php -v
# Must be 8.5 or higher
Check required extensions:
php -m | grep -E "json|pdo|mbstring"
Symptom:
PHP Fatal error: Uncaught Error: Call to undefined function json_encode()
Solution:
Install missing PHP extension:
# Ubuntu/Debian
sudo apt-get install php8.5-json
# macOS with Homebrew
brew install php@8.5
# Verify
php -m | grep json
### Configuration Issues Section
```markdown
## Configuration Issues
### Environment Variables Not Loading
**Symptom:**
API key not configured
**Checklist:**
1. **Verify `.env` file exists:**
```bash
ls -la .env
Check variable is set:
grep "PACKAGE_API_KEY" .env
Verify no syntax errors:
# Values with spaces need quotes
PACKAGE_NAME="My App Name" # ✅ Correct
PACKAGE_NAME=My App Name # ❌ Wrong
Clear config cache:
php artisan config:clear # Laravel
rm var/cache/config.php # Other frameworks
Symptom:
Configuration error: 'timeout' must be a positive integer
Solution:
Check config/package.php:
// ❌ Wrong
'timeout' => '30', // String instead of int
// ✅ Correct
'timeout' => 30, // Integer
### Runtime Errors Section
```markdown
## Runtime Errors
### Connection Timeout
**Symptom:**
Error: Connection timed out after 30 seconds
**Possible Causes:**
1. **Network issues** — Check connectivity
2. **Firewall blocking** — Check outbound rules
3. **Service down** — Check status page
4. **Timeout too short** — Increase timeout
**Solutions:**
```php
// Increase timeout
$client = new Client([
'timeout' => 60, // 60 seconds
]);
# Test connectivity
curl -v https://api.example.com/health
Symptom:
{
"error": {
"code": "RATE_LIMITED",
"message": "Too many requests"
}
}
Solutions:
Implement backoff:
$client = new Client([
'retry' => [
'max_attempts' => 3,
'delay' => 1000, // ms
],
]);
Cache responses:
$cache = new RedisCache();
$client = new Client(['cache' => $cache]);
Upgrade plan for higher limits
Symptom:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted
Solutions:
Process in batches:
foreach ($client->paginate(100) as $batch) {
process($batch);
}
Increase memory limit:
ini_set('memory_limit', '256M');
Use generators:
foreach ($client->stream() as $item) {
yield process($item);
}
### FAQ Section
```markdown
## FAQ
### General
<details>
<summary><strong>Q: What PHP version is required?</strong></summary>
PHP 8.5 or higher is required. Check your version:
```bash
php -v
</details>
<details>
<summary><strong>Q: Is this library production-ready?</strong></summary>
Yes, the library is used in production by many projects. We follow semantic versioning and maintain backward compatibility within major versions.
</details>Use environment-specific .env files:
.env # Base configuration
.env.local # Local overrides (not committed)
.env.test # Test environment
.env.prod # Production environment
</details>
<details>
<summary><strong>Q: Can I use environment variables directly?</strong></summary>
Yes, you can pass configuration directly:
$client = new Client([
'api_key' => getenv('MY_API_KEY'),
]);
</details>
$client = new Client([
'cache' => new RedisCache(),
'pool_size' => 10,
]);
</details>
```
## Getting Help
### Before Asking for Help
1. **Search existing issues:** [GitHub Issues](https://github.com/vendor/package/issues)
2. **Check documentation:** [Docs](https://docs.example.com)
3. **Review changelog:** [CHANGELOG.md](CHANGELOG.md)
### Collect Debug Information
Run this command and include output in your issue:
```bash
php -v
composer show vendor/package
php -m | grep -E "json|pdo|curl"
Create an issue with:
## Complete Example
```markdown
# Troubleshooting
## Quick Fixes
| Problem | Solution |
|---------|----------|
| Class not found | `composer dump-autoload` |
| Permission denied | `chmod -R 755 var/` |
| Config missing | Check `.env` exists |
## Common Errors
### "Invalid API Key"
**Symptom:**
Error: Invalid API key provided
**Solutions:**
1. Verify key in `.env`:
```bash
grep "API_KEY" .env
Check for extra whitespace:
API_KEY=abc123 # ✅ No quotes needed
API_KEY= abc123 # ❌ Extra space
Regenerate key at dashboard
Free tier allows 100 requests/hour. Upgrade for more.
</details>
## Generation Instructions
When generating troubleshooting docs:
1. **Start with symptoms** — What user sees
2. **Explain causes** — Why it happens
3. **Provide solutions** — Step-by-step fixes
4. **Include verification** — How to confirm fix
5. **Use collapsible FAQ** — Reduce scrolling
6. **Link to help** — Where to get more support
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
日本語の概要は準備中です。原文の説明を表示しています。
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
日本語の概要は準備中です。原文の説明を表示しています。
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
日本語の概要は準備中です。原文の説明を表示しています。