design-view
Design views with proper includes/excludes and basic layout. Use for include patterns, tag filtering, and simple rank hints. For advanced styling/navigation, use customize-view.
Browse published AI skills maintained by a-scolan. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
30Repository stars across indexed skills
30Repository forks
30Average repository stars per indexed skill
1Repository stars may repeat across skills from the same repository.
Design views with proper includes/excludes and basic layout. Use for include patterns, tag filtering, and simple rank hints. For advanced styling/navigation, use customize-view.
Create Architecture Decision Records (ADRs) documenting WHY decisions were made. Uses standard ADR format (Status/Context/Decision/Consequences).
Quick reference for available element kinds and relationship types from shared specifications.
Load project context before making changes. Use when starting work to check available element kinds, relationship types, and tags.
Create sequence views showing temporal flows and user interactions. Uses plain arrows with descriptive labels (no relationship kinds).
Validate model correctness using MCP tools. Checks element references, relationships, view definitions, and syntax.
Create typed relationships with FQN, proper kinds (calls/async/reads/writes), descriptive labels, and no return relationships.
Structure multi-project workspaces with shared specifications. Use template project for new projects, organize by domain/team/layer.
Create elements with proper naming (PascalCase kinds, camelCase vars), required metadata (technology, description), and correct hierarchy.
Model deployment infrastructure (environments, zones, VMs, apps) with proper hierarchy and instanceOf links. Organize zones into tiers (DMZ, App, Data, Processing) with rich descriptions including VLAN/network...
Apply common patterns (external integration, async processing, multi-tier, caching). Provides tested templates.
Manage likec4.config.json includes and image aliases. Ensures relative paths and preserves existing configuration. Support multi-file organization (system-model + system-views + deployment + operations).
Diagnose common LikeC4 errors (element not found, unknown kinds, invalid relationships). Provides causes and solutions.
Advanced view features: styling (colors, shapes, style predicates), layout control (autoLayout, rank hints), and navigation (navigateTo, links).
Systematic naming for deployment nodes (VMs, zones, environments) enables consistent infrastructure documentation. Use {Environment}{Service}Vm for VMs, {Tier} for zones, and include VLAN/network details.
Use metadata for system models (business/technical context) and markdown tables for deployment models (infrastructure specs). Makes models queryable and self-documenting.
C4 modeling methodology - design system hierarchy top-to-bottom from Context to Components. Ensures consistent, stakeholder-focused architecture documentation.
Organize deployment infrastructure into logical tiers (DMZ → AppTier → ProcTier → DataTier) with clear responsibility separation and firewall rules between zones.
Write descriptions for system model elements using metadata blocks for structured business/technical data. Makes architecture queryable and reportable.
Document firewall rules between tiers and define scaling strategies (horizontal vs vertical) for production infrastructure.
Model deployment infrastructure hierarchy (environments, zones, VMs, apps) with proper nesting and instanceOf links. Show parent-child relationships clearly.
Model C1 Context - define system boundary, identify external actors, external systems, and relationships. Establishes "what is the system and who uses it?"
Model C2 Containers - break system into major deployable units with independent runtime boundaries. Show container relationships and technologies.
Design views with proper parent context and neighboring elements. Include C1/C2/C3 hierarchy, include patterns, and view organization into folders.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.