Skip to content

armelhbobdad/oh-my-skills / .claude/skills/skf-create-stack-skill

skf-create-stack-skill

Verified

Consolidated project stack skill with integration patterns — code-mode (analyzes manifests) or compose-mode (synthesizes from existing skills + architecture doc). Use when the user requests to "create a stack skill", "forge a stack", or "stack this project".

references/integration-patterns.md

View on GitHub
<!-- Config: communicate in {communication_language}. -->

# Integration Pattern Detection Rules

## Integration Pattern Types

### Type 1: Middleware Chain
Libraries connected in a processing pipeline.
- **Signal:** Sequential function calls passing output of one library to another
- **Example:** `express` + `cors` — cors middleware registered on express app

### Type 2: Shared Types
Libraries exchanging type definitions or data structures.
- **Signal:** Type imports from one library used as parameters/returns in another
- **Example:** `react` + `react-router` — Router components accepting React elements

### Type 3: Configuration Bridge
One library configuring or initializing another.
- **Signal:** Config objects or initialization calls referencing both libraries
- **Example:** `next` + `tailwindcss` — Tailwind configured via next.config

### Type 4: Event Handler
Libraries connected through event emission/handling patterns.
- **Signal:** Event listeners from one library triggering actions in another
- **Example:** `socket.io` + `redis` — Redis pub/sub driving socket events

### Type 5: Adapter/Wrapper
One library wrapping another to provide a unified interface.
- **Signal:** Thin wrapper functions delegating to underlying library
- **Example:** `prisma` + `zod` — Zod schemas validating Prisma model inputs

### Type 6: State Sharing
Libraries sharing application state or context.
- **Signal:** Shared state stores, context providers, or global singletons
- **Example:** `react` + `zustand` — Zustand stores consumed in React components

## Output Format

For each detected integration:
```
Library A + Library B
  Type: [pattern type]
  Files: [count] files with co-imports
  Key files: [top 3 files by integration density]
  Pattern: [brief description of how they integrate]
  Confidence: [the pair tier step 5 §3 takes from skf-render-stack-metadata.py, with the detection-method qualifier in parens, e.g. `T1-low (grep-co-import)`, `T1 (grep-co-import)`, `T1-low (architecture-co-mention) [composed]`. Integration detection is co-import evidence from the import counts, never AST: do not label integrations "AST-verified".]
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall