compact-agent 1.10.0 → 1.11.0

package/resources/ecc/commands/feature-development.md

@@ -1,38 +0,0 @@
----
-name: feature-development
-description: Workflow command scaffold for feature-development in everything-claude-code.
-allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
----
-
-# /feature-development
-
-Use this workflow when working on **feature-development** in `everything-claude-code`.
-
-## Goal
-
-Standard feature implementation workflow
-
-## Common Files
-
-- `manifests/*`
-- `schemas/*`
-- `**/*.test.*`
-- `**/api/**`
-
-## Suggested Sequence
-
-1. Understand the current state and failure mode before editing.
-2. Make the smallest coherent change that satisfies the workflow goal.
-3. Run the most relevant verification for touched files.
-4. Summarize what changed and what still needs review.
-
-## Typical Commit Signals
-
-- Add feature implementation
-- Add tests for feature
-- Update documentation
-
-## Notes
-
-- Treat this as a scaffold, not a hard-coded script.
-- Update the command if the workflow evolves materially.

package/resources/ecc/rules/common-development-workflow.md

@@ -1,33 +0,0 @@
----
-description: "Development workflow: plan, TDD, review, commit pipeline"
-alwaysApply: true
----
-# Development Workflow
-
-> This rule extends the git workflow rule with the full feature development process that happens before git operations.
-
-The Feature Implementation Workflow describes the development pipeline: planning, TDD, code review, and then committing to git.
-
-## Feature Implementation Workflow
-
-1. **Plan First**
-   - Use **planner** agent to create implementation plan
-   - Identify dependencies and risks
-   - Break down into phases
-
-2. **TDD Approach**
-   - Use **tdd-guide** agent
-   - Write tests first (RED)
-   - Implement to pass tests (GREEN)
-   - Refactor (IMPROVE)
-   - Verify 80%+ coverage
-
-3. **Code Review**
-   - Use **code-reviewer** agent immediately after writing code
-   - Address CRITICAL and HIGH issues
-   - Fix MEDIUM issues when possible
-
-4. **Commit & Push**
-   - Detailed commit messages
-   - Follow conventional commits format
-   - See the git workflow rule for commit message format and PR process

package/resources/ecc/rules/kotlin-coding-style.md

@@ -1,39 +0,0 @@
----
-description: "Kotlin coding style extending common rules"
-globs: ["**/*.kt", "**/*.kts", "**/build.gradle.kts"]
-alwaysApply: false
----
-# Kotlin Coding Style
-
-> This file extends the common coding style rule with Kotlin-specific content.
-
-## Formatting
-
-- Auto-formatting via **ktfmt** or **ktlint** (configured in `kotlin-hooks.md`)
-- Use trailing commas in multiline declarations
-
-## Immutability
-
-The global immutability requirement is enforced in the common coding style rule.
-For Kotlin specifically:
-
-- Prefer `val` over `var`
-- Use immutable collection types (`List`, `Map`, `Set`)
-- Use `data class` with `copy()` for immutable updates
-
-## Null Safety
-
-- Avoid `!!` -- use `?.`, `?:`, `require`, or `checkNotNull`
-- Handle platform types explicitly at Java interop boundaries
-
-## Expression Bodies
-
-Prefer expression bodies for single-expression functions:
-
-```kotlin
-fun isAdult(age: Int): Boolean = age >= 18
-```
-
-## Reference
-
-See skill: `kotlin-patterns` for comprehensive Kotlin idioms and patterns.

package/resources/ecc/rules/kotlin-patterns.md

@@ -1,50 +0,0 @@
----
-description: "Kotlin patterns extending common rules"
-globs: ["**/*.kt", "**/*.kts", "**/build.gradle.kts"]
-alwaysApply: false
----
-# Kotlin Patterns
-
-> This file extends the common patterns rule with Kotlin-specific content.
-
-## Sealed Classes
-
-Use sealed classes/interfaces for exhaustive type hierarchies:
-
-```kotlin
-sealed class Result<out T> {
-    data class Success<T>(val data: T) : Result<T>()
-    data class Failure(val error: AppError) : Result<Nothing>()
-}
-```
-
-## Extension Functions
-
-Add behavior without inheritance, scoped to where they're used:
-
-```kotlin
-fun String.toSlug(): String =
-    lowercase().replace(Regex("[^a-z0-9\\s-]"), "").replace(Regex("\\s+"), "-")
-```
-
-## Scope Functions
-
-- `let`: Transform nullable or scoped result
-- `apply`: Configure an object
-- `also`: Side effects
-- Avoid nesting scope functions
-
-## Dependency Injection
-
-Use Koin for DI in Ktor projects:
-
-```kotlin
-val appModule = module {
-    single<UserRepository> { ExposedUserRepository(get()) }
-    single { UserService(get()) }
-}
-```
-
-## Reference
-
-See skill: `kotlin-patterns` for comprehensive Kotlin patterns including coroutines, DSL builders, and delegation.

package/resources/ecc/rules/kotlin-security.md

@@ -1,58 +0,0 @@
----
-description: "Kotlin security extending common rules"
-globs: ["**/*.kt", "**/*.kts", "**/build.gradle.kts"]
-alwaysApply: false
----
-# Kotlin Security
-
-> This file extends the common security rule with Kotlin-specific content.
-
-## Secret Management
-
-```kotlin
-val apiKey = System.getenv("API_KEY")
-    ?: throw IllegalStateException("API_KEY not configured")
-```
-
-## SQL Injection Prevention
-
-Always use Exposed's parameterized queries:
-
-```kotlin
-// Good: Parameterized via Exposed DSL
-UsersTable.selectAll().where { UsersTable.email eq email }
-
-// Bad: String interpolation in raw SQL
-exec("SELECT * FROM users WHERE email = '$email'")
-```
-
-## Authentication
-
-Use Ktor's Auth plugin with JWT:
-
-```kotlin
-install(Authentication) {
-    jwt("jwt") {
-        verifier(
-            JWT.require(Algorithm.HMAC256(secret))
-                .withAudience(audience)
-                .withIssuer(issuer)
-                .build()
-        )
-        validate { credential ->
-            val payload = credential.payload
-            if (payload.audience.contains(audience) &&
-                payload.issuer == issuer &&
-                payload.subject != null) {
-                JWTPrincipal(payload)
-            } else {
-                null
-            }
-        }
-    }
-}
-```
-
-## Null Safety as Security
-
-Kotlin's type system prevents null-related vulnerabilities -- avoid `!!` to maintain this guarantee.

package/resources/ecc/rules/kotlin-testing.md

@@ -1,38 +0,0 @@
----
-description: "Kotlin testing extending common rules"
-globs: ["**/*.kt", "**/*.kts", "**/build.gradle.kts"]
-alwaysApply: false
----
-# Kotlin Testing
-
-> This file extends the common testing rule with Kotlin-specific content.
-
-## Framework
-
-Use **Kotest** with spec styles (StringSpec, FunSpec, BehaviorSpec) and **MockK** for mocking.
-
-## Coroutine Testing
-
-Use `runTest` from `kotlinx-coroutines-test`:
-
-```kotlin
-test("async operation completes") {
-    runTest {
-        val result = service.fetchData()
-        result.shouldNotBeEmpty()
-    }
-}
-```
-
-## Coverage
-
-Use **Kover** for coverage reporting:
-
-```bash
-./gradlew koverHtmlReport
-./gradlew koverVerify
-```
-
-## Reference
-
-See skill: `kotlin-testing` for detailed Kotest patterns, MockK usage, and property-based testing.

package/resources/ecc/rules/php-coding-style.md

@@ -1,25 +0,0 @@
----
-description: "PHP coding style extending common rules"
-globs: ["**/*.php", "**/composer.json"]
-alwaysApply: false
----
-# PHP Coding Style
-
-> This file extends the common coding style rule with PHP specific content.
-
-## Standards
-
-- Follow **PSR-12** formatting and naming conventions.
-- Prefer `declare(strict_types=1);` in application code.
-- Use scalar type hints, return types, and typed properties everywhere new code permits.
-
-## Immutability
-
-- Prefer immutable DTOs and value objects for data crossing service boundaries.
-- Use `readonly` properties or immutable constructors for request/response payloads where possible.
-- Keep arrays for simple maps; promote business-critical structures into explicit classes.
-
-## Formatting
-
-- Use **PHP-CS-Fixer** or **Laravel Pint** for formatting.
-- Use **PHPStan** or **Psalm** for static analysis.

package/resources/ecc/rules/php-patterns.md

@@ -1,23 +0,0 @@
----
-description: "PHP patterns extending common rules"
-globs: ["**/*.php", "**/composer.json"]
-alwaysApply: false
----
-# PHP Patterns
-
-> This file extends the common patterns rule with PHP specific content.
-
-## Thin Controllers, Explicit Services
-
-- Keep controllers focused on transport: auth, validation, serialization, status codes.
-- Move business rules into application/domain services that are easy to test without HTTP bootstrapping.
-
-## DTOs and Value Objects
-
-- Replace shape-heavy associative arrays with DTOs for requests, commands, and external API payloads.
-- Use value objects for money, identifiers, and constrained concepts.
-
-## Dependency Injection
-
-- Depend on interfaces or narrow service contracts, not framework globals.
-- Pass collaborators through constructors so services are testable without service-locator lookups.

package/resources/ecc/rules/php-security.md

@@ -1,24 +0,0 @@
----
-description: "PHP security extending common rules"
-globs: ["**/*.php", "**/composer.lock", "**/composer.json"]
-alwaysApply: false
----
-# PHP Security
-
-> This file extends the common security rule with PHP specific content.
-
-## Database Safety
-
-- Use prepared statements (`PDO`, Doctrine, Eloquent query builder) for all dynamic queries.
-- Scope ORM mass-assignment carefully and whitelist writable fields.
-
-## Secrets and Dependencies
-
-- Load secrets from environment variables or a secret manager, never from committed config files.
-- Run `composer audit` in CI and review package trust before adding dependencies.
-
-## Auth and Session Safety
-
-- Use `password_hash()` / `password_verify()` for password storage.
-- Regenerate session identifiers after authentication and privilege changes.
-- Enforce CSRF protection on state-changing web requests.

package/resources/ecc/rules/php-testing.md

@@ -1,26 +0,0 @@
----
-description: "PHP testing extending common rules"
-globs: ["**/*.php", "**/phpunit.xml", "**/phpunit.xml.dist", "**/composer.json"]
-alwaysApply: false
----
-# PHP Testing
-
-> This file extends the common testing rule with PHP specific content.
-
-## Framework
-
-Use **PHPUnit** as the default test framework. **Pest** is also acceptable when the project already uses it.
-
-## Coverage
-
-```bash
-vendor/bin/phpunit --coverage-text
-# or
-vendor/bin/pest --coverage
-```
-
-## Test Organization
-
-- Separate fast unit tests from framework/database integration tests.
-- Use factory/builders for fixtures instead of large hand-written arrays.
-- Keep HTTP/controller tests focused on transport and validation; move business rules into service-level tests.

package/resources/ecc/rules/swift-hooks.md

@@ -1,20 +0,0 @@
----
-description: "Swift hooks extending common rules"
-globs: ["**/*.swift", "**/Package.swift"]
-alwaysApply: false
----
-# Swift Hooks
-
-> This file extends the common hooks rule with Swift specific content.
-
-## PostToolUse Hooks
-
-Configure in `~/.claude/settings.json`:
-
-- **SwiftFormat**: Auto-format `.swift` files after edit
-- **SwiftLint**: Run lint checks after editing `.swift` files
-- **swift build**: Type-check modified packages after edit
-
-## Warning
-
-Flag `print()` statements -- use `os.Logger` or structured logging instead for production code.

package/resources/ecc/rules/typescript-coding-style.md

@@ -1,63 +0,0 @@
----
-description: "TypeScript coding style extending common rules"
-globs: ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]
-alwaysApply: false
----
-# TypeScript/JavaScript Coding Style
-
-> This file extends the common coding style rule with TypeScript/JavaScript specific content.
-
-## Immutability
-
-Use spread operator for immutable updates:
-
-```typescript
-// WRONG: Mutation
-function updateUser(user, name) {
-  user.name = name  // MUTATION!
-  return user
-}
-
-// CORRECT: Immutability
-function updateUser(user, name) {
-  return {
-    ...user,
-    name
-  }
-}
-```
-
-## Error Handling
-
-Use async/await with try-catch:
-
-```typescript
-try {
-  const result = await riskyOperation()
-  return result
-} catch (error) {
-  console.error('Operation failed:', error)
-  throw new Error('Detailed user-friendly message')
-}
-```
-
-## Input Validation
-
-Use Zod for schema-based validation:
-
-```typescript
-import { z } from 'zod'
-
-const schema = z.object({
-  email: z.string().email(),
-  age: z.number().int().min(0).max(150)
-})
-
-const validated = schema.parse(input)
-```
-
-## Console.log
-
-- No `console.log` statements in production code
-- Use proper logging libraries instead
-- See hooks for automatic detection

package/resources/ecc/rules/typescript-testing.md

@@ -1,16 +0,0 @@
----
-description: "TypeScript testing extending common rules"
-globs: ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]
-alwaysApply: false
----
-# TypeScript/JavaScript Testing
-
-> This file extends the common testing rule with TypeScript/JavaScript specific content.
-
-## E2E Testing
-
-Use **Playwright** as the E2E testing framework for critical user flows.
-
-## Agent Support
-
-- **e2e-runner** - Playwright E2E testing specialist

package/resources/ecc/skills/agent-introspection-debugging/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Agent Introspection Debugging"
-  short_description: "Structured self-debugging for AI agent failures"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $agent-introspection-debugging to diagnose and recover from an AI agent failure."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/agent-sort/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Agent Sort"
-  short_description: "Evidence-backed ECC install planning"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $agent-sort to build an evidence-backed ECC install plan."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/api-design/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "API Design"
-  short_description: "REST API design patterns and best practices"
-  brand_color: "#F97316"
-  default_prompt: "Use $api-design to design production REST API resources and responses."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/article-writing/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Article Writing"
-  short_description: "Long-form content in a supplied voice"
-  brand_color: "#B45309"
-  default_prompt: "Use $article-writing to draft polished long-form content in the supplied voice."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/backend-patterns/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Backend Patterns"
-  short_description: "API, database, and server-side patterns"
-  brand_color: "#F59E0B"
-  default_prompt: "Use $backend-patterns to apply backend architecture and API patterns."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/brand-voice/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Brand Voice"
-  short_description: "Source-derived writing style profiles"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $brand-voice to derive and reuse a source-grounded writing style."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/bun-runtime/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Bun Runtime"
-  short_description: "Bun runtime, package manager, and test runner"
-  brand_color: "#FBF0DF"
-  default_prompt: "Use $bun-runtime to choose and apply Bun runtime workflows."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/coding-standards/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Coding Standards"
-  short_description: "Cross-project coding conventions and review"
-  brand_color: "#3B82F6"
-  default_prompt: "Use $coding-standards to review code against cross-project standards."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/content-engine/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Content Engine"
-  short_description: "Platform-native content systems and campaigns"
-  brand_color: "#DC2626"
-  default_prompt: "Use $content-engine to turn source material into platform-native content."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/crosspost/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Crosspost"
-  short_description: "Multi-platform social distribution"
-  brand_color: "#EC4899"
-  default_prompt: "Use $crosspost to adapt content for multiple social platforms."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/deep-research/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Deep Research"
-  short_description: "Multi-source cited research reports"
-  brand_color: "#6366F1"
-  default_prompt: "Use $deep-research to produce a cited multi-source research report."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/dmux-workflows/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "dmux Workflows"
-  short_description: "Multi-agent orchestration with dmux"
-  brand_color: "#14B8A6"
-  default_prompt: "Use $dmux-workflows to orchestrate parallel agent sessions with dmux."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/documentation-lookup/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Documentation Lookup"
-  short_description: "Current library docs via Context7"
-  brand_color: "#6366F1"
-  default_prompt: "Use $documentation-lookup to fetch current library documentation via Context7."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/e2e-testing/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "E2E Testing"
-  short_description: "Playwright E2E testing patterns"
-  brand_color: "#06B6D4"
-  default_prompt: "Use $e2e-testing to design Playwright end-to-end test coverage."
-policy:
-  allow_implicit_invocation: true

package/resources/ecc/skills/eval-harness/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Eval Harness"
-  short_description: "Eval-driven development harnesses"
-  brand_color: "#EC4899"
-  default_prompt: "Use $eval-harness to define eval-driven development checks."
-policy:
-  allow_implicit_invocation: true