Windmill Trigger Type Checklist
windmill-labs/windmill
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
Selects and routes to the right architecture paradigm. An agent skill from athola/claude-night-market.
Install Architecture Paradigms
$ npx skills add athola/claude-night-market --skill architecture-paradigms -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install athola/claude-night-market architecture-paradigms --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigms .claude/skills/architecture-paradigms && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "architecture-paradigms" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigms into .claude/skills/architecture-paradigms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigms", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigmsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add athola/claude-night-market --skill architecture-paradigms -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install athola/claude-night-market architecture-paradigms --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigms .agents/skills/architecture-paradigms && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architecture-paradigms" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigms into .agents/skills/architecture-paradigms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigms", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add athola/claude-night-market --skill architecture-paradigms -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install athola/claude-night-market architecture-paradigms --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigms .cursor/skills/architecture-paradigms && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "architecture-paradigms" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigms into .cursor/skills/architecture-paradigms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigms", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/athola/claude-night-market.git --path plugins/archetypes/skills/architecture-paradigms--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add athola/claude-night-market --skill architecture-paradigms -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install athola/claude-night-market architecture-paradigms --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigms .gemini/skills/architecture-paradigms && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "architecture-paradigms" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigms into .gemini/skills/architecture-paradigms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigms", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install athola/claude-night-market architecture-paradigmsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add athola/claude-night-market --skill architecture-paradigms -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigms .github/skills/architecture-paradigms && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "architecture-paradigms" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigms into .github/skills/architecture-paradigms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigms", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add athola/claude-night-market --skill architecture-paradigms -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install athola/claude-night-market architecture-paradigms --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/archetypes/skills/architecture-paradigms .opencode/skills/architecture-paradigms && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "architecture-paradigms" agent skill from https://github.com/athola/claude-night-market/tree/master/plugins/archetypes/skills/architecture-paradigms into .opencode/skills/architecture-paradigms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-paradigms", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
architecture-paradigms- GitHub stars
- 341
- Token cost
- ~2k tokens
- SKILL.md length
- 665 words
- Files
- 1
- Skills in repo
- 152
- Repo updated
- First seen
- Licence
- MIT
At a glance
Selects and routes to the right architecture paradigm. An agent skill from athola/claude-night-market.
- Works in 3 steps: Define Your Needs → Evaluate Paradigms → Load Paradigm Skill for Implementation
- Choosing patterns for a new system
- SKILL.md covers When NOT To Use, Quick Scenario Router, 3-Step Selection Workflow and Available Paradigm Skills, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Architecture Paradigms is an agent skill from athola/claude-night-market. Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Event-driven systems. The repository describes itself as: 23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context… The licence is MIT.
When your agent uses it
- Choosing patterns for a new system
- Comparing trade-offs before making architecture decisions
Example prompts
- “Use the architecture-paradigms skill to select and routes to the right architecture paradigm. An agent skill from athola/claude-night-market”
- “/architecture-paradigms”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9f3eb00. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Architecture Paradigms loads about 2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 665 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from athola/claude-night-market at commit 9f3eb00, republished under its MIT licence (© athola). 665 words, ~2,031 tokens.
Download SKILL.mdSave it as
.claude/skills/architecture-paradigms/SKILL.md (or your agent's skills folder).- name
- architecture-paradigms
- description
- Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.
- alwaysApply
- false
- category
- architecture-decision
- tags
- architecture, patterns, selection, implementation, adr
- dependencies
- architecture-paradigm-functional-core, architecture-paradigm-hexagonal, architecture-paradigm-domain-driven, architecture-paradigm-cqrs-es…
- usage_patterns
- paradigm-selection, architecture-review, implementation-planning, adr-creation
- complexity
- intermediate
- model_hint
- standard
- estimated_tokens
- 280
When NOT To Use
- The paradigm is already chosen, so go straight to that paradigm's skill
- Reviewing an existing design against its ADRs (use
pensive:architecture-review)
Architecture Paradigm Router
This skill helps you select the right architecture paradigm(s) for your system, then routes you to the specific paradigm skill for implementation details.
Quick Scenario Router
Match your needs to the recommended paradigm:
| Your Scenario | Primary Paradigm | Load Skill |
|---|---|---|
| Enterprise app with multiple teams | Microservices or Modular Monolith | architecture-paradigm-microservices or architecture-paradigm-modular-monolith |
| Complex business rules & testing | Functional Core, Imperative Shell | architecture-paradigm-functional-core |
| Real-time/event processing | Event-Driven Architecture | architecture-paradigm-event-driven |
| Legacy system modernization | Hexagonal (Ports & Adapters) | architecture-paradigm-hexagonal |
| Cloud-native/bursty workloads | Serverless | architecture-paradigm-serverless |
| ETL/data processing pipeline | Pipeline Architecture | architecture-paradigm-pipeline |
| Simple CRUD app | Layered Architecture | architecture-paradigm-layered |
| Command/query separation | CQRS and Event Sourcing | architecture-paradigm-cqrs-es |
| Rich business rules to model | Domain-Driven Design | architecture-paradigm-domain-driven |
One of these is not like the others. Domain-Driven Design answers "what are the concepts and what do we call them." The rest answer "where does the code go." DDD composes with a structural paradigm (commonly layered, hexagonal, or modular monolith) rather than competing with it, so selecting it does not mean deselecting one of the others.
3-Step Selection Workflow
Step 1: Define Your Needs
Primary Concerns (select all that apply):
- Testability: Isolate business logic →
functional-coreorhexagonal - Team Autonomy: Independent deployment →
microservicesormodular-monolith - Infrastructure Flexibility: Swap databases/frameworks →
hexagonal - Real-time Scaling: Variable loads with events →
event-drivenorspace-based - Simplicity: Maintainable without complexity →
layeredormodular-monolith - Legacy Integration: Work with existing systems →
hexagonalormicrokernel
System Context:
- Team Size:
< 5→ Layered/Functional Core |5-15→ Modular Monolith |15-50→ Microservices |50+→ Microservices/Space-Based - Domain Complexity:
Simple→ Layered |Moderate→ Hexagonal/Modular Monolith |Complex→ Functional Core/CQRS |Highly Complex→ Microservices/Event-Driven
Step 2: Evaluate Paradigms
Based on your needs from Step 1, review these options:
For Testability & Business Logic
- Load
architecture-paradigm-functional-core- Isolates business logic from infrastructure - Load
architecture-paradigm-hexagonal- Clear domain/infrastructure boundaries
For Team Autonomy
- Load
architecture-paradigm-microservices- Independent deployment and scaling - Load
architecture-paradigm-modular-monolith- Team autonomy without distributed complexity
For Infrastructure Flexibility
- Load
architecture-paradigm-hexagonal- Swap infrastructure without domain changes
For Simplicity & Maintainability
- Load
architecture-paradigm-layered- Simple, well-understood separation
For Rich Business Rules
- Load
architecture-paradigm-domain-driven- Models the business in its own language. Pair it with whichever structural paradigm you picked above; it does not replace one. Skip it when the domain is CRUD over a form, where the model would just be the schema under a new name.
For Real-time Event Processing
- Load
architecture-paradigm-event-driven- Scalable, decoupled processing - Load
architecture-paradigm-space-based- In-memory data grids for linear scalability
For Legacy Integration
- Load
architecture-paradigm-microkernel- Plugin architecture for extensible platforms - Load
architecture-paradigm-hexagonal- Adapters for external systems
Show full SKILL.md (246 more words)Show less
Step 3: Load Paradigm Skill for Implementation
Once you've selected your paradigm(s), load the specific skill for detailed guidance:
# Example: You selected Hexagonal Architecture
Skill(archetypes:architecture-paradigm-hexagonal)The individual paradigm skill provides:
- ✅ Complete implementation guide
- ✅ ADR templates
- ✅ Migration checklist
- ✅ Code examples
- ✅ Testing strategies
- ✅ Risk assessments
Available Paradigm Skills
| Paradigm | Complexity | Team Size | Best For | Skill Name |
|---|---|---|---|---|
| Functional Core | Medium | Small-Large | Complex business logic | architecture-paradigm-functional-core |
| Hexagonal | Medium | Small-Large | Infrastructure changes | architecture-paradigm-hexagonal |
| Layered | Low | Small-Medium | Simple domains | architecture-paradigm-layered |
| Modular Monolith | Medium | Medium-Large | Evolving systems | architecture-paradigm-modular-monolith |
| Microservices | High | Large | Complex domains | architecture-paradigm-microservices |
| Event-Driven | High | Medium-Large | Real-time processing | architecture-paradigm-event-driven |
| CQRS and ES | High | Medium-Large | Audit trails | architecture-paradigm-cqrs-es |
| Service-Based | Medium | Medium | Coarse-grained services | architecture-paradigm-service-based |
| Serverless | Medium | Small-Medium | Cloud-native/bursty | architecture-paradigm-serverless |
| Microkernel | Medium | Small-Medium | Plugin systems | architecture-paradigm-microkernel |
| Space-Based | High | Large | Linear scalability | architecture-paradigm-space-based |
| Pipeline | Low | Small-Medium | ETL workflows | architecture-paradigm-pipeline |
| Client-Server | Low | Small | Traditional apps | architecture-paradigm-client-server |
| Domain-Driven Design | Medium | Small-Large | Rich business rules (composes with the above) | architecture-paradigm-domain-driven |
Integration with Other Skills
- Architecture Review: Use this skill first to select paradigms, then
/architecture-reviewfor evaluation - Implementation Planning: Select paradigms here, then
/writing-plansfor detailed task breakdown - Refactoring: Identify target paradigms here, then use paradigm-specific skills for migration strategies
Exit Criteria
- At least one paradigm is selected with clear rationale
- Specific paradigm skill has been loaded for detailed guidance
- Ready to create ADR or implementation plan
Next Steps
- Load the specific paradigm skill - Use
Skill(archetypes:architecture-paradigm-NAME) - Generate an ADR - Use the paradigm's ADR templates
- Create implementation plan - Use paradigm's migration checklist
- Set up monitoring - Track success metrics from paradigm guidance
© athola, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/archetypes/skills/architecture-paradigms of athola/claude-night-market.
Open the folder on GitHubat commit 9f3eb00
Compare with similar skills
Architecture Paradigms next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Architecture Paradigms this skillathola/claude-night-market | 341 | — | ~2k | Automated safety check: Pass | MIT | |
| Windmill Trigger Type Checklistwindmill-labs/windmill | 18k | — | ~4.7k | Automated safety check: Pass | Custom licence | |
| Dynamic Consistency BoundariesAxonIQ/AxonFramework | 3.6k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Opensource Guide Coachcalf-ai/calfkit-sdk | 149 | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| NestJS Modular Monolith Architecttech-leads-club/agent-skills | 7k | — | ~3.9k | Automated safety check: Pass | CC-BY-4.0 | |
| Create Pluginmarcus/sidecar | 1.1k | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Dynamic Consistency Boundaries
AxonIQ/AxonFramework
Explain and reason about Dynamic Consistency Boundaries (DCB) and how Axon Framework 5 and Axon Server implement them.
Opensource Guide Coach
calf-ai/calfkit-sdk
A skill your agent uses when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding…
NestJS Modular Monolith Architect
tech-leads-club/agent-skills
Designs scalable NestJS modular monoliths with domain-driven design, Clean Architecture layers and optional CQRS, defining bounded contexts and strict module boundaries.
Create Plugin
marcus/sidecar
Create new sidecar plugins implementing the plugin.Plugin interface, rendering views with Bubble Tea, handling keyboard input via keymap contexts, and integrating with the app shell (footer hints…
Adobe App Builder Action Scaffolder
adobe/skills
Scaffolds, implements, deploys and debugs Adobe Runtime actions in App Builder projects, with templates for webhooks, events, database CRUD, sequences and Asset Compute workers.
More from athola/claude-night-market
All 152 skills in this repoNight Market Diagnostics Toolkit
athola/claude-night-market
Run and interpret repo diagnostic scripts (ratchets, validators, token stats).
Skills Eval
athola/claude-night-market
Evaluate Claude skill quality through auditing. An agent skill from athola/claude-night-market.
Agent Teams
athola/claude-night-market
Coordinates Claude agent teams via filesystem protocol. An agent skill from athola/claude-night-market.
Delegation Core
athola/claude-night-market
Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer).
Elegant Code
athola/claude-night-market
Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage.
Skill Library Mission
athola/claude-night-market
Build a project skill library in .claude/skills/ via discovery, parallel authoring, and review.
Related
Categories
Questions about Architecture Paradigms
What does Architecture Paradigms do?
Selects and routes to the right architecture paradigm. An agent skill from athola/claude-night-market. Architecture Paradigms is an agent skill from athola/claude-night-market. Selects and routes to the right architecture paradigm.
When should I use Architecture Paradigms?
Architecture Paradigms fits situations like: choosing patterns for a new system; comparing trade-offs before making architecture decisions.
How do I install Architecture Paradigms in Claude Code?
Run `npx skills add athola/claude-night-market --skill architecture-paradigms -a claude-code`. Or copy the skill folder (plugins/archetypes/skills/architecture-paradigms in athola/claude-night-market) into .claude/skills/architecture-paradigms in your project. Claude Code loads it when a task matches its description.
How do I install Architecture Paradigms in Codex?
Run `npx skills add athola/claude-night-market --skill architecture-paradigms -a codex`. Or copy the skill folder (plugins/archetypes/skills/architecture-paradigms in athola/claude-night-market) into .agents/skills/architecture-paradigms in your project. Codex loads it when a task matches its description.
Can I use Architecture Paradigms in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add athola/claude-night-market --skill architecture-paradigms -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-paradigms, .gemini/skills/architecture-paradigms, .github/skills/architecture-paradigms and .opencode/skills/architecture-paradigms in your project.
What does Architecture Paradigms need to run?
SKILL.md names no scripts, command-line tools or credentials: Architecture Paradigms is instructions for the agent only.
Does Architecture Paradigms access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architecture Paradigms safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Architecture Paradigms use?
Architecture Paradigms is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Architecture Paradigms use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Architecture Paradigms?
Skills that share tags, products or a category with Architecture Paradigms: Windmill Trigger Type Checklist (windmill-labs/windmill, 18k stars), Dynamic Consistency Boundaries (AxonIQ/AxonFramework, 3.6k stars), Opensource Guide Coach (calf-ai/calfkit-sdk, 149 stars) and NestJS Modular Monolith Architect (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architecture Paradigms?
athola (a GitHub user) maintains it in athola/claude-night-market, which has 341 GitHub stars. The repository holds 152 skills in this directory. The repository was last updated on October 9, 2026.
Source: athola/claude-night-market on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.