efoo
Official@efoo-team
Offers architectural governance, database schema design, and code review analysis for enterprise software engineering teams.
Agent Skills by efoo
Showing 8 vetted skills indexed across 1 GitHub repositories.
efoo-teamlangfuse
Query Langfuse REST API traces, observations, scores, and datasets.
efoo-teamreview-plan
Analyze implementation plans against external specifications and internal standards.
efoo-teamdatabase-design
Name database tables and columns using domain concepts.
efoo-teammastra-ai-architecture-rules
Provide design principles for safe, scalable Mastra AI service architectures.
efoo-teammodule-boundary-design
Analyze change patterns, responsibilities, and dependencies to design module boundaries.
efoo-teamrefactor-mindset
Reorganize software architecture to improve modularity and separation of concerns.
efoo-teamformation-designer
Design AI formation configurations with model classification, slot requirements, and fallback policies.
efoo-teamgithub-pull-request
Analyze code diffs into hierarchical layers for pull request descriptions.
Frequently Asked Questions About efoo
FAQPage SchemaWhat specific engineering tasks does efoo support?▼
efoo supports architectural design, database schema naming, and code review documentation. It enables engineers to define module boundaries, structure pull request descriptions from diffs, and establish design principles for service architectures, ensuring consistency across complex software projects.
Which technical personas benefit from these capabilities?▼
Software architects, lead developers, and database administrators benefit from these capabilities. These personas use the provided design principles and analysis patterns to maintain code quality, enforce modularity, and standardize naming conventions within large-scale enterprise repositories.
What are the prerequisites for implementing these design patterns?▼
Implementation requires an existing codebase or schema definition to analyze. Users must provide access to code diffs, database entity relationships, or architectural specifications to allow the system to evaluate module boundaries and generate compliant documentation or design configurations.