All authors
Claude Skills by leaderiop
github.com/leaderiop35 skills0 installs104 views
- C4 Mermaid SyntaxComplete Mermaid.js C4 diagram syntax reference with ASCII format for console output. Use when creating C4 diagrams in Mermaid syntax within markdown files, when writing C4Context, C4Container, C4Component, C4Dynamic, or C4Deployment diagram code blocks, when looking up Mermaid C4 macros for persons, systems, containers, components, boundaries, relationships, deployment nodes, or styling. Use when embedding C4 architecture diagrams in README files, specification documents, ADRs, or any markdo...Votes: 0GitHub stars: 22
- C4 MethodologyC4 model methodology for software architecture documentation. Use when deciding which C4 diagram level to create, when scoping architecture diagrams by audience, when ensuring cross-level consistency between C4 diagrams, when extracting architecture from a TypeScript monorepo into C4 abstractions, when mapping hexagonal architecture layers to C4 vocabulary, or when reviewing C4 diagrams for correctness. Use when a user asks about C4 modeling concepts, abstraction levels, element types, or dia...Votes: 0GitHub stars: 22
- Spec TypesAuthor domain type specification files in a spec's types/ directory. Each file documents types for a domain with field tables, immutability annotations, discriminant fields, and behavior cross-references. Use when creating type specifications, auditing type completeness, or documenting domain types.Votes: 0GitHub stars: 22
- Spec VisualSub-orchestrator for the visual/ directory in a spec. Manages the Flux Pattern view specification structure including pages, components, elements, stores, events, actions, and workflows. Handles triad authoring (YAML + markdown wireframe + Gherkin feature).Votes: 0GitHub stars: 22
- Specforge AuthoringOrchestrator for writing .spec files that the SpecForge compiler turns into a typed, validated graph -- for any domain the project's extensions declare (software specs, product plans, marketing, pharma/GxP procedures, operations). Checks first which extensions the project loads and which entity kinds they declare, writes only those kinds, prefers typed edits (specforge new/set/link), and delegates to the per-kind child skills when a builtin extension is loaded. Use when writing new .spec file...Votes: 0GitHub stars: 22
- Specforge Behaviors DslWrite behavior blocks in .spec files (the behavior kind is declared by the builtin @specforge/software extension). Each behavior declares one operation's contract with a snake_case ID, a contract statement using RFC 2119 keywords, links to invariants, types, ports, events and features, verify obligations (with @specforge/testing) and Design-by-Contract blocks requires/ensures/maintains (with @specforge/formal). Use when specifying what exactly a system does in a specific situation.Votes: 0GitHub stars: 22
- Specforge Constraints DslWrite constraint blocks in .spec files (the constraint kind is declared by the builtin @specforge/governance extension). Each constraint declares a measurable limit or requirement -- performance, security, regulatory, compatibility -- with a snake_case ID, a description, a category, a priority (critical/high/medium/low), a metric and threshold, and links to the behaviors it constrains, the invariants it protects and the features it governs. Use when defining quality attributes or rules with t...Votes: 0GitHub stars: 22
- Specforge Decisions DslWrite decision (ADR) blocks in .spec files (the decision kind is declared by the builtin @specforge/governance extension). Each decision records a significant choice with a snake_case ID, a status lifecycle, context/decision/consequences, alternatives, deciders, and links to the invariants it protects, the constraints it imposes and the features it affects. Use when documenting why something is done a certain way -- an architecture choice, a process rule, a policy.Votes: 0GitHub stars: 22
- Specforge Deliverables DslWrite deliverable blocks in .spec files (the deliverable kind is declared by the builtin @specforge/product extension). Each deliverable declares a shippable artifact with a snake_case ID, an artifact type, a status, the journeys it supports, the modules it contains and the milestones it is tracked under. Use when describing what actually ships -- apps, services, CLIs, libraries, extensions, documentation.Votes: 0GitHub stars: 22
- Specforge DomainSpecForge product knowledge -- the domain-free engine that turns what an organisation knows (its things, their relationships and the rules they must obey) into one typed, validated graph that people and AI agents read and change through CLI, MCP and LSP. Covers the five parts (extensions, graph, validation, surfaces, AI models), the five structural keywords, the builtin starter extensions, what is shipped versus planned, and the CLI. Use when explaining what SpecForge is, reasoning about the ...Votes: 0GitHub stars: 22
- Specforge Events DslWrite event blocks in .spec files (the event kind is declared by the builtin @specforge/software extension). Each event declares something that happened, with a snake_case ID, a payload type reference, a channel name, verify obligations (with @specforge/testing) and sync/protocol/process links (with @specforge/formal). Use when making a system's reactive behavior explicit and traceable.Votes: 0GitHub stars: 22
- Specforge Failure Modes DslWrite failure_mode blocks in .spec files (the failure_mode kind is declared by the builtin @specforge/governance extension). Each failure_mode is an FMEA entry with a snake_case ID, a cause and an effect, severity/occurrence/detection ratings before and after mitigation, a mitigation, and links to the invariant it threatens, the behaviors it affects and the features it threatens. Use when analysing what can go wrong and how bad it would be, in software or in a regulated process.Votes: 0GitHub stars: 22
- Specforge Features DslWrite feature blocks in .spec files (the feature kind is declared by the builtin @specforge/product extension). Each feature declares a user-facing capability with a snake_case ID, problem/solution framing, acceptance criteria, status, priority, owner and effort; the behaviors that implement it name it in their `features` field. Features take no verify statements. Use when grouping work into coherent units of value for product planning, in software or any other product.Votes: 0GitHub stars: 22
- Specforge Invariants DslWrite invariant blocks in .spec files (the invariant kind is declared by the builtin @specforge/governance extension). Each invariant declares a rule that must always hold, with a snake_case ID, a guarantee statement using RFC 2119 keywords, a risk level (critical/high/medium/low), verify obligations (with @specforge/testing) and an optional machine-checkable expression (with @specforge/formal). Use when defining what must ALWAYS be true.Votes: 0GitHub stars: 22
- Specforge Journeys DslWrite journey blocks in .spec files (the journey kind is declared by the builtin @specforge/product extension). Each journey declares a user flow with a snake_case ID, the persona who takes it, the channels it happens through, the features it exercises and an ordered step-by-step flow. Use when describing how a specific kind of user experiences a product -- software, a clinic visit, a course enrollment or a customer purchase.Votes: 0GitHub stars: 22
- Specforge Milestones DslWrite milestone blocks in .spec files (the milestone kind is declared by the builtin @specforge/product extension). Each milestone declares a planning phase with a snake_case ID, a status lifecycle, the features it must deliver, exit criteria, dates, blockers and dependencies on other milestones. Use when defining when things ship and what must be true before a phase is complete, for any kind of project.Votes: 0GitHub stars: 22
- Specforge Modules DslWrite module blocks in .spec files (the module kind is declared by the builtin @specforge/product extension). Each module declares a structural component -- a package, a subsystem, a workstream or a program area -- with a snake_case ID, a family, the features it contains and a dependency graph between modules. Use when making explicit which component delivers which features, in software or any other organisation.Votes: 0GitHub stars: 22
- Specforge Ports DslWrite port interface blocks in .spec files (the port kind is declared by the builtin @specforge/software extension). Each port declares an interface contract with a direction (inbound/outbound/bidirectional), a category, and `method` signatures with typed parameters and Result return types. Use when defining boundaries between the domain and external systems in hexagonal architecture.Votes: 0GitHub stars: 22
- Specforge Refs DslWrite ref external reference declarations in .spec files. `ref` is one of the five structural keywords of the core grammar, available in every project whatever extensions it loads. Covers the one-line form (ref gh.issue:42 \"Title\"), the block form with metadata, and naming declared refs in an entity's refs list or in prose. Use when linking entities of any domain to outside resources: issues, tickets, designs, SOPs, documents.Votes: 0GitHub stars: 22
- Specforge Spec BlockWrite the spec block, the project's root entity (one of the five structural keywords of the core grammar), and know where configuration really lives: specforge.json holds the project name, version, spec_root, the extensions to load, providers and registries. Use when initializing a SpecForge project in any domain, changing which extensions a project loads, or editing the root spec block.Votes: 0GitHub stars: 22
- Specforge Terms DslWrite term blocks in .spec files (the term kind is declared by the builtin @specforge/product extension). Each term declares a glossary entry as its own entity, with a snake_case ID, a definition, usage context, aliases, related terms and the module that owns it. Use when establishing precise vocabulary for any domain -- software, pharma, marketing, operations -- to prevent terminology drift.Votes: 0GitHub stars: 22
- Specforge Types DslWrite type definitions in .spec files (the type kind is declared by the builtin @specforge/software extension). Supports struct types with one `name Type` member per line and annotations (@readonly, @unique, @literal, @optional), union types (type X \"Title\" = a | b | c), and error types with the _tag pattern. Use when defining data shapes for domain entities, commands, errors, event payloads and value objects.Votes: 0GitHub stars: 22
- Uml DiagramsGenerate UML diagrams using Mermaid.js syntax for software architecture documentation, code visualization, and design communication. Use when creating class diagrams, sequence diagrams, state diagrams, component diagrams, flowcharts, entity-relationship diagrams, or any visual representation of code structure and behavior. Use when documenting TypeScript interfaces, ports/adapters architecture, dependency injection graphs, domain models, API interactions, state machines, data flows, or system...Votes: 0GitHub stars: 22
- T Ns ContextRoutes a request about the codebaseVotes: 0GitHub stars: 22
- T Plan PhasePlan the phase, then check the plansVotes: 0GitHub stars: 22
- T StatsShow the project's statisticsVotes: 0GitHub stars: 22
- T Ns ContextRoutes a request about the codebaseVotes: 0GitHub stars: 22
- T Plan PhasePlan the phase, then check the plansVotes: 0GitHub stars: 22
- T StatsShow the project's statisticsVotes: 0GitHub stars: 22
- T Ns ContextRoutes a request about the codebaseVotes: 0GitHub stars: 22
- T Plan PhasePlan the phase, then check the plansVotes: 0GitHub stars: 22
- T StatsShow the project's statisticsVotes: 0GitHub stars: 22
- Claude CodeRetroactively verify threat mitigations for a completed phaseVotes: 0GitHub stars: 22
- CodexRetroactively verify threat mitigations for a completed phaseVotes: 0GitHub stars: 22
- CursorRetroactively verify threat mitigations for a completed phaseVotes: 0GitHub stars: 22