mirror of https://github.com/secondsky/claude-skills.git synced 2026-09-18 19:54:22 +08:00

Files

T

secondsky c1afc6db8b refactor: Flatten plugin structure to fix skill discovery (v3.2.0)

BREAKING CHANGE: All plugin paths changed from nested to flat structure

Problem:
- Only 11 out of 169 skills appeared in Claude Code's system prompt
- v3.1.0 updated marketplace.json but didn't migrate directory structure
- Mismatch: marketplace expected `./plugins/skill-name` but files were at
  `./plugins/category/skills/skill-name`

Solution:
- Moved all 169 skills from `plugins/*/skills/*` to `plugins/*` (flat)
- Removed 66 empty category directories (api, cloudflare, testing, etc.)
- Updated marketplace.json with correct flat paths (all 169 entries)
- Updated scripts to work with flat structure:
  - generate-marketplace.sh: removed nested loop logic
  - sync-plugins.sh: simplified to single loop
  - Added flatten-plugin-structure.sh migration tool

Migration Details:
- Used git mv to preserve history for all 169 skills
- Handled name collisions via temporary directories
- Validated: 0 errors, 169 skills successfully migrated

Results:
- ✅ All 169 skills at `plugins/*/` level
- ✅ marketplace.json: 169 valid entries
- ✅ No nested skills/ directories remain
- ✅ Scripts updated and tested

This completes the migration started in v3.1.0 (commit 677abf8) and
resolves skill discovery issues.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2025-12-24 02:03:18 +01:00

1.6 KiB

Raw Permalink Blame History

Microservices Patterns Skill

Design distributed systems with service boundaries, event-driven communication, and resilience patterns.

Overview

This skill provides comprehensive guidance on microservices architecture including service decomposition, inter-service communication, data management, and resilience patterns for building reliable distributed systems.

When to Use

Decomposing monoliths into microservices
Designing service boundaries and contracts
Implementing inter-service communication
Managing distributed data and transactions
Building resilient distributed systems
Implementing service discovery and load balancing
Designing event-driven architectures

Core Patterns

Service Decomposition

By business capability
By subdomain (DDD)
Strangler Fig pattern for gradual migration
API Gateway for aggregation

Communication

Synchronous: REST, gRPC, GraphQL
Asynchronous: Event streaming (Kafka), Message queues (RabbitMQ, SQS)
Request/Response vs Event-Driven

Data Management

Database per service (no shared databases)
Saga pattern for distributed transactions
Eventual consistency
Compensating actions

Resilience

Circuit Breaker pattern
Retry with exponential backoff
Bulkhead isolation
Health checks and service discovery

Auto-Trigger Keywords

microservices architecture
service decomposition
distributed systems
event driven architecture
saga pattern
circuit breaker
API gateway
service mesh
inter-service communication
database per service
eventual consistency

Source

Adapted from wshobson/agents

1.6 KiB Raw Permalink Blame History