oornnery/design
skills/design/SKILL.md
Design guidance for APIs, user interfaces, and BFF boundaries. Load when shaping external contracts, response models, component systems, accessibility, or frontend/backend boundaries.
development
Updated Jun 4, 2026
$ install --global
skillsauthnpx skillsauth add oornnery/.agents designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 7:41 AM300.7s4 files scanned
SKILL.md
- name:
- design
- description:
- Design guidance for APIs, user interfaces, and BFF boundaries. Load when shaping external contracts, response models, component systems, accessibility, or frontend/backend boundaries.
Design
Use skill when main question = how system presents to clients/users.
When to Load Each Reference
| Situation | Read |
| ------------------------------------------- | ----------------------------------- |
| routes, contracts, errors, pagination | references/api.md |
| tokens, components, states, accessibility | references/ui.md |
| frontend-specific aggregation and reshaping | references/bff.md |
| both surface types matter | read dominant one first, then other |
Workflow
- decide whether problem is API-facing, UI-facing, or both
- define contract before impl details
- keep naming, states, failure behavior explicit
- add BFF only if frontend needs aggregation/reshaping
- prefer stable patterns over clever shortcuts
- update
DESIGN.mdwhen API, UI, BFF, or product/design decisions need to persist - keep surface consistent across related endpoints/components
Shared Rules
- design happy path + failure path together
- keep APIs/components predictable before flexible
- add complexity only when real use case demands
- durable design decisions belong in
DESIGN.md; short active notes belong in.spec/state.md
Related Skills
oornnery/skills/verification
development
VerifiedTrustedCommunity
--- name: verification description: Discover and run project validation gates: format, lint, typecheck, LSP diagnostics, tests, build, static security checks, dependency audits, and RTK output handling. Use before claiming work is complete, when fixing broken checks, or when setting up a validation plan. --- # Verification Use this skill to prove changes with the strongest practical checks the repo already supports. ## Discovery Order 1. Read task aliases: `package.json`, `pyproject.toml`, `
SKILL.mdUpdated Jun 4, 2026
oornnery/uv-script
tools
VerifiedTrustedCommunity
Build, review, or validate standalone Python scripts run with uv inline metadata. Use for one-file automation, operational scripts, script dependencies, shebangs, idempotency, safety, representative runs, and promoting scripts to packages.
SKILL.mdUpdated Jun 4, 2026
oornnery/python-library
development
VerifiedTrustedCommunity
Build, review, or validate Python packages and libraries where public API stability, packaging metadata, imports, examples, changelogs, build output, and compatibility matter.
SKILL.mdUpdated Jun 4, 2026
oornnery/python-cli
tools
VerifiedTrustedCommunity
Build, review, or validate Python command-line applications and terminal tools. Use for argparse, Typer, Rich, Textual-adjacent CLI UX, stdout/stderr contracts, exit codes, automation-friendly flags, help output, and CLI tests.
SKILL.mdUpdated Jun 4, 2026