cc-codeconductor 0.2.9 → 0.3.0

package/presets/opencode/skills/android/SKILL.md

@@ -0,0 +1,119 @@
+---
+id: android
+version: 1.0.0
+name: Android + Kotlin (Jetpack Compose & Media3)
+description: >
+  Provides expert knowledge for building modern native Android apps using Kotlin, Jetpack Compose, Material Design 3, MVI architecture, Hilt dependency injection, and Media3/ExoPlayer.
+
+user-invokable: true
+license: MIT
+metadata:
+  author: lgzarturo
+  category: mobile
+
+compatibility:
+  tools: [claude, codex, gemini, agy, opencode]
+  stacks:
+    languages: [kotlin, java]
+    frameworks: [android]
+
+risk:
+  level: medium
+  can_execute_shell: true
+  can_modify_files: true
+  requires_network: false
+
+inputs: []
+
+outputs: []
+
+quality:
+  reviewed_by: codeconductor-core
+  version: 0.1.0
+---
+
+# Android + Kotlin (Jetpack Compose & Media3)
+
+This playbook defines the architecture, UI design system, performance guidelines, and testing strategy for native Android applications.
+
+---
+
+## 1. Lead Architect & Modularization
+
+### Architecture (MVI / MVVM with Clean Architecture)
+- Prefer **MVI (Model-View-Intent)** for state management. Ensure a strict unidirectional data flow:
+  - **UiState**: Single source of truth for the UI state.
+  - **UiIntent**: Actions initiated by the user or system.
+  - **UiEffect**: One-time events (navigation, toasts, snackbars).
+- Separate the project into clean logical modules:
+  - `app`: Application entry point, launcher activity, global dependency injection configuration.
+  - `core`: Shared resources, network layer, media playback logic (ExoPlayer/Media3), storage.
+  - `feature`: Individual business features (isolated and independent of other features).
+
+### Dependency Injection (Hilt)
+- Annotate the Application class with `@HiltAndroidApp`.
+- Annotate Activities and Fragments with `@AndroidEntryPoint`.
+- Use constructor injection for ViewModels with `@HiltViewModel`.
+
+---
+
+## 2. Jetpack Compose UI/UX
+
+### Recomposition & State Management
+- Consume `StateFlow` from ViewModels safely using `collectAsStateWithLifecycle()` to respect the activity lifecycle.
+- Keep data models immutable. Mark configuration classes with `@Immutable` or `@Stable` to prevent redundant recompositions.
+- Use `contentType` and `key` in `LazyColumn` and `LazyRow` to optimize item recycling and rendering performance.
+- Avoid fixed hardcoded margins. Apply `WindowInsets` to support modern edge-to-edge screens.
+
+---
+
+## 3. Performance & Multimedia (Media3 / ExoPlayer)
+
+### Playback & Services
+- Run `ExoPlayer` / `Media3` inside a robust `Foreground Service` (using `MediaSessionService`) to ensure playback continues when the app is in the background.
+- Clean up resources: release player instances in `onDestroy` or when the service is stopped.
+- Control wake locks strictly to avoid draining the user's battery when playback is paused.
+
+### Kotlin Coroutines & Threading
+- Always inject `CoroutineDispatcher` instances instead of hardcoding them:
+  - `Dispatchers.IO`: Database access, network operations, file reading.
+  - `Dispatchers.Default`: CPU-intensive operations (parsing JSON, filtering large lists).
+  - `Dispatchers.Main`: UI modifications and light interactions.
+
+### R8 & Resource Optimization
+- Enable shrinking and obfuscation in production builds:
+  - `isMinifyEnabled = true`
+  - `isShrinkResources = true`
+- Convert all static images to the modern `WebP` format to minimize the application binary size.
+
+---
+
+## 4. Quality Assurance & Automated Testing
+
+### Unit Testing
+- Use JUnit 5 and MockK for mocking dependencies.
+- Test ViewModels and Reducers by asserting StateFlow updates. Use `Turbine` to easily test Kotlin Flows.
+- Mock all multimedia/ExoPlayer components to avoid loading actual audio/video resources in unit tests.
+
+### UI Testing
+- Create UI tests using Compose test rules: `createComposeRule()` or `createAndroidComposeRule<MainActivity>()`.
+- Assert correct rendering, visibility states, and user interactions without executing real network calls.
+
+---
+
+## 5. Key Gradle & ADB Commands
+
+Use these commands for building, checking code style, running tests, and profiling performance:
+
+| Command | Action |
+| ------- | ------ |
+| `./gradlew init` | Initialize a new Gradle project structure. |
+| `./gradlew app:dependencies` | List all dependencies of the application module. |
+| `./gradlew assembleDebug` | Validate compilation and generate debug APK. |
+| `./gradlew ktlintCheck` | Run KtLint check to enforce Kotlin style guidelines. |
+| `./gradlew lintDebug` | Run Android Lint tool to inspect code quality and UI issues. |
+| `./gradlew testDebugUnitTest` | Run unit tests for debug build variant. |
+| `./gradlew connectedAndroidTest` | Run instrumented UI tests on connected emulator or device. |
+| `./gradlew assembleRelease` | Generate release build variant with R8 optimizations. |
+| `adb shell dumpsys batterystats` | Profile system battery consumption metrics. |
+| `adb shell am dumpheap <package> heap.hprof` | Dump application heap memory file for profiling. |

package/presets/opencode/skills/conductor-setup/SKILL.md

@@ -0,0 +1,125 @@
+---
+name: conductor-setup
+description: Configure a Rails project to work with Conductor (parallel coding agents)
+allowed-tools: Bash(chmod *), Bash(bundle *), Bash(npm *), Bash(script/server)
+context: fork
+risk: unknown
+source: community
+metadata:
+  author: Shpigford
+  version: "1.0"
+---
+
+Set up this Rails project for Conductor, the Mac app for parallel coding agents.
+
+## When to Use
+- You need to configure a Rails project so it runs correctly inside Conductor workspaces.
+- The project should support parallel coding agents with isolated ports, Redis settings, and shared secrets.
+- You want the standard `conductor.json`, `bin/conductor-setup`, and `script/server` scaffolding for a Rails repo.
+
+# What to Create
+
+## 1. conductor.json (project root)
+
+Create `conductor.json` in the project root if it doesn't already exist:
+
+```json
+{
+  "scripts": {
+    "setup": "bin/conductor-setup",
+    "run": "script/server"
+  }
+}
+```
+
+## 2. bin/conductor-setup (executable)
+
+Create `bin/conductor-setup` if it doesn't already exist:
+
+```bash
+#!/bin/bash
+set -e
+
+# Symlink .env from repo root (where secrets live, outside worktrees)
+[ -f "$CONDUCTOR_ROOT_PATH/.env" ] && ln -sf "$CONDUCTOR_ROOT_PATH/.env" .env
+
+# Symlink Rails master key
+[ -f "$CONDUCTOR_ROOT_PATH/config/master.key" ] && ln -sf "$CONDUCTOR_ROOT_PATH/config/master.key" config/master.key
+
+# Install dependencies
+bundle install
+npm install
+```
+
+Make it executable with `chmod +x bin/conductor-setup`.
+
+## 3. script/server (executable)
+
+Create the `script` directory if needed, then create `script/server` if it doesn't already exist:
+
+```bash
+#!/bin/bash
+
+# === Port Configuration ===
+export PORT=${CONDUCTOR_PORT:-3000}
+export VITE_RUBY_PORT=$((PORT + 1000))
+
+# === Redis Isolation ===
+if [ -n "$CONDUCTOR_WORKSPACE_NAME" ]; then
+  HASH=$(printf '%s' "$CONDUCTOR_WORKSPACE_NAME" | cksum | cut -d' ' -f1)
+  REDIS_DB=$((HASH % 16))
+  export REDIS_URL="redis://localhost:6379/${REDIS_DB}"
+fi
+
+exec bin/dev
+```
+
+Make it executable with `chmod +x script/server`.
+
+## 4. Update Rails Config Files
+
+For each of the following files, if they exist and contain Redis configuration, update them to use `ENV.fetch('REDIS_URL', ...)` or `ENV['REDIS_URL']` with a fallback:
+
+### config/initializers/sidekiq.rb
+If this file exists and configures Redis, update it to use:
+```ruby
+redis_url = ENV.fetch('REDIS_URL', 'redis://localhost:6379/0')
+```
+
+### config/cable.yml
+If this file exists, update the development adapter to use:
+```yaml
+development:
+  adapter: redis
+  url: <%= ENV.fetch('REDIS_URL', 'redis://localhost:6379/1') %>
+```
+
+### config/environments/development.rb
+If this file configures Redis for caching, update to use:
+```ruby
+config.cache_store = :redis_cache_store, { url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0') }
+```
+
+### config/initializers/rack_attack.rb
+If this file exists and configures a Redis cache store, update to use:
+```ruby
+Rack::Attack.cache.store = ActiveSupport::Cache::RedisCacheStore.new(url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0'))
+```
+
+# Implementation Notes
+
+- **Don't overwrite existing files**: Check if conductor.json, bin/conductor-setup, and script/server exist before creating them. If they exist, skip creation and inform the user.
+- **Rails config updates**: Only modify Redis-related configuration. If a file doesn't exist or doesn't use Redis, skip it gracefully.
+- **Create directories as needed**: Create `script/` directory if it doesn't exist.
+
+# Verification
+
+After creating the files:
+1. Confirm all Conductor files exist and scripts are executable
+2. Run `script/server` to verify it starts without errors
+3. Check that Rails configs properly reference `ENV['REDIS_URL']` or `ENV.fetch('REDIS_URL', ...)`
+
+## Limitations
+- Use this skill only when the task clearly matches the scope described above.
+- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

package/presets/opencode/skills/find-skills/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** https://skills.sh/
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Check the Leaderboard First
+
+Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
+
+For example, top skills for web development include:
+- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
+- `anthropics/skills` — Frontend design, document processing (100K+ installs)
+
+### Step 3: Search for Skills
+
+If the leaderboard doesn't cover the user's need, run the find command:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+### Step 4: Verify Quality Before Recommending
+
+**Do not recommend a skill based solely on search results.** Always verify:
+
+1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.
+2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
+3. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
+
+### Step 5: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install count and source
+3. The install command they can run
+4. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+(185K installs)
+
+To install it:
+npx skills add vercel-labs/agent-skills@react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
+```
+
+### Step 6: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```

package/presets/opencode/skills/laravel-specialist/SKILL.md

@@ -0,0 +1,264 @@
+---
+name: laravel-specialist
+description: Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers, implementing Sanctum auth flows, building Livewire components, optimising Eloquent queries, or writing Pest/PHPUnit tests for Laravel features.
+license: MIT
+metadata:
+  author: https://github.com/Jeffallan
+  version: "1.1.0"
+  domain: backend
+  triggers: Laravel, Eloquent, PHP framework, Laravel API, Artisan, Blade templates, Laravel queues, Livewire, Laravel testing, Sanctum, Horizon
+  role: specialist
+  scope: implementation
+  output-format: code
+  related-skills: fullstack-guardian, test-master, devops-engineer, security-reviewer
+---
+
+# Laravel Specialist
+
+Senior Laravel specialist with deep expertise in Laravel 10+, Eloquent ORM, and modern PHP 8.2+ development.
+
+## Core Workflow
+
+1. **Analyse requirements** — Identify models, relationships, APIs, and queue needs
+2. **Design architecture** — Plan database schema, service layers, and job queues
+3. **Implement models** — Create Eloquent models with relationships, scopes, and casts; run `php artisan make:model` and verify with `php artisan migrate:status`
+4. **Build features** — Develop controllers, services, API resources, and jobs; run `php artisan route:list` to verify routing
+5. **Test thoroughly** — Write feature and unit tests; run `php artisan test` before considering any step complete (target >85% coverage)
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Eloquent ORM | `references/eloquent.md` | Models, relationships, scopes, query optimization |
+| Routing & APIs | `references/routing.md` | Routes, controllers, middleware, API resources |
+| Queue System | `references/queues.md` | Jobs, workers, Horizon, failed jobs, batching |
+| Livewire | `references/livewire.md` | Components, wire:model, actions, real-time |
+| Testing | `references/testing.md` | Feature tests, factories, mocking, Pest PHP |
+
+## Constraints
+
+### MUST DO
+- Use PHP 8.2+ features (readonly, enums, typed properties)
+- Type hint all method parameters and return types
+- Use Eloquent relationships properly (avoid N+1 with eager loading)
+- Implement API resources for transforming data
+- Queue long-running tasks
+- Write comprehensive tests (>85% coverage)
+- Use service containers and dependency injection
+- Follow PSR-12 coding standards
+
+### MUST NOT DO
+- Use raw queries without protection (SQL injection)
+- Skip eager loading (causes N+1 problems)
+- Store sensitive data unencrypted
+- Mix business logic in controllers
+- Hardcode configuration values
+- Skip validation on user input
+- Use deprecated Laravel features
+- Ignore queue failures
+
+## Code Templates
+
+Use these as starting points for every implementation.
+
+### Eloquent Model
+
+```php
+<?php
+
+declare(strict_types=1);
+
+namespace App\Models;
+
+use Illuminate\Database\Eloquent\Factories\HasFactory;
+use Illuminate\Database\Eloquent\Model;
+use Illuminate\Database\Eloquent\Relations\BelongsTo;
+use Illuminate\Database\Eloquent\Relations\HasMany;
+use Illuminate\Database\Eloquent\SoftDeletes;
+
+final class Post extends Model
+{
+    use HasFactory, SoftDeletes;
+
+    protected $fillable = ['title', 'body', 'status', 'user_id'];
+
+    protected $casts = [
+        'status' => PostStatus::class, // backed enum
+        'published_at' => 'immutable_datetime',
+    ];
+
+    // Relationships — always eager-load via ::with() at call site
+    public function author(): BelongsTo
+    {
+        return $this->belongsTo(User::class, 'user_id');
+    }
+
+    public function comments(): HasMany
+    {
+        return $this->hasMany(Comment::class);
+    }
+
+    // Local scope
+    public function scopePublished(Builder $query): Builder
+    {
+        return $query->where('status', PostStatus::Published);
+    }
+}
+```
+
+### Migration
+
+```php
+<?php
+
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+return new class extends Migration
+{
+    public function up(): void
+    {
+        Schema::create('posts', function (Blueprint $table): void {
+            $table->id();
+            $table->foreignId('user_id')->constrained()->cascadeOnDelete();
+            $table->string('title');
+            $table->text('body');
+            $table->string('status')->default('draft');
+            $table->timestamp('published_at')->nullable();
+            $table->softDeletes();
+            $table->timestamps();
+        });
+    }
+
+    public function down(): void
+    {
+        Schema::dropIfExists('posts');
+    }
+};
+```
+
+### API Resource
+
+```php
+<?php
+
+declare(strict_types=1);
+
+namespace App\Http\Resources;
+
+use Illuminate\Http\Request;
+use Illuminate\Http\Resources\Json\JsonResource;
+
+final class PostResource extends JsonResource
+{
+    public function toArray(Request $request): array
+    {
+        return [
+            'id'           => $this->id,
+            'title'        => $this->title,
+            'body'         => $this->body,
+            'status'       => $this->status->value,
+            'published_at' => $this->published_at?->toIso8601String(),
+            'author'       => new UserResource($this->whenLoaded('author')),
+            'comments'     => CommentResource::collection($this->whenLoaded('comments')),
+        ];
+    }
+}
+```
+
+### Queued Job
+
+```php
+<?php
+
+declare(strict_types=1);
+
+namespace App\Jobs;
+
+use App\Models\Post;
+use Illuminate\Bus\Queueable;
+use Illuminate\Contracts\Queue\ShouldQueue;
+use Illuminate\Foundation\Bus\Dispatchable;
+use Illuminate\Queue\InteractsWithQueue;
+use Illuminate\Queue\SerializesModels;
+
+final class PublishPost implements ShouldQueue
+{
+    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;
+
+    public int $tries = 3;
+    public int $backoff = 60;
+
+    public function __construct(
+        private readonly Post $post,
+    ) {}
+
+    public function handle(): void
+    {
+        $this->post->update([
+            'status'       => PostStatus::Published,
+            'published_at' => now(),
+        ]);
+    }
+
+    public function failed(\Throwable $e): void
+    {
+        // Log or notify — never silently swallow failures
+        logger()->error('PublishPost failed', ['post' => $this->post->id, 'error' => $e->getMessage()]);
+    }
+}
+```
+
+### Feature Test (Pest)
+
+```php
+<?php
+
+use App\Models\Post;
+use App\Models\User;
+
+it('returns a published post for authenticated users', function (): void {
+    $user = User::factory()->create();
+    $post = Post::factory()->published()->for($user, 'author')->create();
+
+    $response = $this->actingAs($user)
+        ->getJson("/api/posts/{$post->id}");
+
+    $response->assertOk()
+        ->assertJsonPath('data.status', 'published')
+        ->assertJsonPath('data.author.id', $user->id);
+});
+
+it('queues a publish job when a draft is submitted', function (): void {
+    Queue::fake();
+    $user = User::factory()->create();
+    $post = Post::factory()->draft()->for($user, 'author')->create();
+
+    $this->actingAs($user)
+        ->postJson("/api/posts/{$post->id}/publish")
+        ->assertAccepted();
+
+    Queue::assertPushed(PublishPost::class, fn ($job) => $job->post->is($post));
+});
+```
+
+## Validation Checkpoints
+
+Run these at each workflow stage to confirm correctness before proceeding:
+
+| Stage | Command | Expected Result |
+|-------|---------|-----------------|
+| After migration | `php artisan migrate:status` | All migrations show `Ran` |
+| After routing | `php artisan route:list --path=api` | New routes appear with correct verbs |
+| After job dispatch | `php artisan queue:work --once` | Job processes without exception |
+| After implementation | `php artisan test --coverage` | >85% coverage, 0 failures |
+| Before PR | `./vendor/bin/pint --test` | PSR-12 linting passes |
+
+## Knowledge Reference
+
+Laravel 10+, Eloquent ORM, PHP 8.2+, API resources, Sanctum/Passport, queues, Horizon, Livewire, Inertia, Octane, Pest/PHPUnit, Redis, broadcasting, events/listeners, notifications, task scheduling
+
+[Documentation](https://jeffallan.github.io/claude-skills/skills/backend/laravel-specialist/)