iClinic - Software médico para clínicas e consultórios
Official@iclinic · Ribeirão Preto
Software médico para clínicas e consultórios
Agent Skills by iClinic - Software médico para clínicas e consultórios
Showing 11 vetted skills indexed across 1 GitHub repositories.
design
Translate vague ideas into formal technical designs with JIRA and Figma context.
test-driven-development
Guide developers through the TDD cycle with npm test feedback.
systematic-debugging
Identify root causes of software bugs through observation, hypothesis testing, and verification.
auto-documentation
Analyze Git diffs to update living feature documentation under docs/afyapowers.
implementing
Orchestrate subagent-driven development tasks during the implementing phase.
reviewing
Automate two-step code reviews for spec compliance and quality.
completing
Finalize features by merging, creating a PR, or summarizing completion.
figma-component
Convert a Figma component into production code with validation and Storybook generation.
writing-plans
Convert scattered design docs into an executable implementation plan with file changes.
verification-before-completion
Run fresh verification commands and capture outputs before claiming completion.
subagent-driven-development
Dispatch subagents per task with dependency-aware waves and self-review.
Frequently Asked Questions About iClinic - Software médico para clínicas e consultórios
FAQPage SchemaWhat specific tasks can engineers perform using iClinic's development framework?▼
Engineers can translate design concepts into executable implementation plans, perform systematic debugging, and execute test-driven development cycles. The framework supports converting Figma components into production code, generating Storybook documentation, and managing two-step code reviews to ensure compliance with technical specifications.
Which personas benefit most from the iClinic development methodology?▼
Software engineers, frontend developers, and quality assurance specialists working on medical practice management systems benefit most. The methodology is designed for technical teams requiring structured, repeatable processes for feature implementation, bug verification, and maintaining high-quality codebases through rigorous testing and documentation standards.
What are the prerequisites for integrating these development practices?▼
Integration requires an existing environment utilizing Figma for design, Git for version control, and npm for test execution. Teams must maintain structured documentation under the docs/afyapowers directory to enable the system to analyze changes and update living feature documentation effectively.