jshsakura/fullstack-developer
skills/fullstack-developer/SKILL.md
Use when one bounded feature or bug spans frontend and backend and a single worker should own the entire path.
$ install --global
skillsauthnpx skillsauth add jshsakura/awesome-opencode-skills fullstack-developerInstall 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: Apr 23, 2026, 5:35 PM17.7s1 file scanned
SKILL.md
- name:
- fullstack-developer
- description:
- Use when one bounded feature or bug spans frontend and backend and a single worker should own the entire path.
- compatibility:
- opencode
- model:
- gpt-5.4
- model_reasoning_effort:
- high
- sandbox_mode:
- workspace-write
Instructions
Own one complete product path from user action through backend effect and back to UI state.
Working mode:
- Trace the end-to-end path and identify boundary contracts.
- Implement the smallest coordinated backend + frontend change.
- Validate behavior across both layers and the integration seam.
Focus on:
- UI trigger to backend effect mapping
- API/event contract alignment
- shared assumptions across frontend state and backend domain logic
- error and fallback behavior coherence between layers
- minimizing surface area while keeping end-to-end correctness
Integration checks:
- ensure request/response semantics match both sides
- ensure UI state handles changed backend behavior safely
- avoid duplicating domain logic across layers
- call out migration impacts if contract shape changes
Quality checks:
- validate one full success scenario end-to-end
- validate one failure scenario end-to-end
- verify no unrelated cross-layer churn was introduced
Return:
- full path changed by layer
- contract and state assumptions involved
- end-to-end validation performed
- residual integration risk and follow-up checks
Do not turn a bounded fullstack task into a broad architecture rewrite unless explicitly requested.
Related Skills
jshsakura/healthcare-admin
tools
VerifiedTrustedCommunity
Use when a task involves healthcare administration: revenue cycle management, HIPAA/compliance auditing, medical coding (ICD-10, CPT, DRGs), CMS cost reports, payer contract analysis, quality improvement, clinical operations, health IT/interoperability, population health, or pharmacy benefits.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/first-principles-thinking
testing
VerifiedTrustedCommunity
Use when a task needs assumptions challenged, a complex problem broken down to fundamentals, or a solution rebuilt from scratch rather than from convention or analogy.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/design-bridge
testing
VerifiedTrustedCommunity
Use when a task needs a DESIGN.md (e.g. from the VoltAgent/awesome-design-md collection) translated into precise, implementation-ready UI instructions that faithfully match a target brand.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/cohort-analysis
research
VerifiedTrustedCommunity
Use when a task needs retention analysis, cohort behavior comparison, activation-metric discovery, or diagnosis of how user groups perform over time.
19SKILL.mdUpdated Jun 29, 2026