favotools_reference

Documents FavoTools architecture, tools, databases, and development rules for PHP and MySQL modules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/elmelali/elmelaliMoltis --skill favotools-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: favotools_reference
Source: https://github.com/elmelali/elmelaliMoltis/tree/main/favotools-reference
Command: npx skills add https://github.com/elmelali/elmelaliMoltis --skill favotools-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This documentation provides a centralized reference for the FavoTools architecture, six tools, and development rules to streamline onboarding and maintenance.

Core Features & Use Cases

  • Centralized technical reference covering architecture, modules, databases, and development guidelines.
  • Clear mapping of the six tools (favolinks, srp, mynotes, favostrategy, favoincome, favoresearch) and their intended use.
  • Versioned documentation with a consistent frontmatter and Markdown body to ensure predictable activation.

Quick Start

Review the favotools-reference documentation to understand the platform's architecture and tooling.

Frequently Asked Questions about favotools_reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document PHP backend architecture and MySQL databases for engineering teams?

You document PHP backend architecture and MySQL databases by enforcing a structured SKILL frontmatter and Markdown body, creating a centralized technical reference for operational guidance and predictable activation across development modules.

What is the best way to maintain centralized development rules and tool references for a PHP platform?

The best way to maintain centralized development rules is using versioned documentation with consistent frontmatter, mapping tool modules and their intended use to ensure predictable onboarding and streamlined maintenance across the engineering team.

Can I use Markdown and frontmatter to manage versioning for software engineering documentation?

Yes, you can use Markdown and frontmatter to manage versioning for software engineering documentation, enforcing a structured format that ensures predictable activation alongside optional assets, references, and scripts directories for comprehensive operational guidance.

Does this documentation reference cover MySQL database schemas and PHP backend tool modules?

Yes, this documentation reference covers MySQL database schemas and PHP backend tool modules, providing clear mapping of six distinct tools and their intended use within the platform's architecture to streamline engineering onboarding.

How do I structure technical documentation to cover architecture, modules, and development guidelines together?

You structure technical documentation by applying a consistent frontmatter for versioning and a Markdown body for operational guidance, centralizing architecture, modules, databases, and development guidelines into a single predictable reference for engineering teams.