neverlbc/-medical-health-system
Overview
This skill provides a full AI-assisted software development workflow focused on practical, repeatable engineering outcomes. It combines a reuse-first "glue code" approach with clear programming philosophy to help plan, structure, implement, and document projects. The assistant is optimized for Vue projects but applies to general web and backend stacks.
How this skill works
It analyzes user requirements to extract explicit goals, hidden needs, and intent, then proposes technology paths, reusable components, and step-by-step plans. For coding tasks it generates and refactors code using a three-layer thinking model (symptom → root → design), enforces naming and quality rules, and suggests project structure and tests. It continually verifies assumptions against available code and docs rather than guessing.
When to use it
- Start a new project and need a layered plan and tech choices
- Standardize or refactor project structure and conventions
- Generate, adapt, or refactor Vue components and app scaffolding
- Design system architecture or evaluate trade-offs for features
- Produce clear developer docs, tests, and onboarding materials
Best practices
- Prefer reuse of proven open-source components; minimize custom glue code
- Always validate library/API availability before coding; do not assume
- Keep functions small and single-responsibility; split when >20 lines or >3 levels deep
- Design stable interfaces and let implementations change; favor reasoning over micro-optimizations
- Write tests and examples before or alongside implementation; verify each step
Example use cases
- Turn a product brief into a layered implementation plan with milestones and chosen libraries
- Bootstrap a Vue project with standardized directory layout, linting, and test scaffolding
- Refactor an existing module to remove redundancy and reduce coupling while preserving behavior
- Design API and data models for a new feature and generate example client code
- Generate end-user and developer documentation for release or onboarding
FAQ
It prioritizes mature, well-documented projects with compatible licenses and minimal invasion into upstream code. Recommendations include alternatives and trade-offs.
Will it change upstream libraries or invent APIs?
No. It never modifies upstream code or fabricates interfaces. It favors composition, adapters, and minimal glue to integrate components.
Can it produce tests and CI configuration?
Yes. It generates unit and integration test templates and suggests CI steps to verify builds, linting, and test runs.
