development

Generate a developer handover guide for Edge Delivery Services projects.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill development-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/development
Command: npx skills add https://github.com/valithedge/etisalatedge --skill development-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a comprehensive, project-specific developer handover guide for Edge Delivery Services projects by analyzing repository structure, custom implementations, and the design system, enabling faster onboarding and maintenance.

Core Features & Use Cases

  • Auto-generates a complete developer guide detailing architecture, blocks, templates, and local dev setup.
  • Documents customizations and design system tokens to accelerate onboarding and reduce knowledge gaps.
  • Supports multi-site repos by mapping site configurations and local development workflows.

Quick Start

Run the handover generator from the project root to produce the Developer Guide.

Frequently Asked Questions about development

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

FAQPage Schema
How do I generate a developer handover guide for an Edge Delivery Services project?

Generate a developer handover guide by analyzing the repository structure, extracting site config via the Config Service API, and mapping customizations to blocks, templates, and scripts to produce a ready-to-publish Markdown document.

What should be included in AEM Edge Delivery Services documentation for developer onboarding?

AEM Edge Delivery Services documentation should include sections on architecture, the design system, custom blocks, templates, and local development setup to ensure comprehensive developer onboarding and reduce knowledge gaps.

Can I create handover documentation for multi-site repoless Edge Delivery Services setups?

Yes, you can create handover documentation for multi-site repoless setups by mapping site configurations and local development workflows, extracting site config via the Config Service API, and synthesizing customizations into a complete guide.

How do I document custom blocks and design system tokens for an Edge Delivery Services project?

Document custom blocks and design system tokens by analyzing the repository structure and identifying project-specific customizations, then synthesizing them into a Markdown guide that details the architecture and local development setup.

Does the generated developer handover guide support PDF conversion for team sharing?

Yes, the generated developer handover guide is produced as a ready-to-publish Markdown document specifically structured to ensure it can be converted to PDF and shared with the team for faster onboarding and maintenance.