functional-designer_skill

This skill designs functional architectures and detailed PHP/CakePHP specifications from requirements to guide development and ensure consistent, scalable

Shell

2

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill masanao-ohba/claude-manifests --skill functional-designer

SKILL.md7.7 KB

Overview

This skill designs functional architecture and detailed specifications for PHP/CakePHP applications from analyzed requirements. It produces component maps, API specs, request lifecycles, data models, and implementation templates that follow CakePHP conventions. The output is actionable: controllers, models, views, services, API endpoints, and database DDL ready for handoff to developers.

How this skill works

I inspect feature requirements and translate them into a structured functional design: component breakdowns, REST API descriptions, data flow diagrams, and CakePHP directory patterns. I produce validation rules, associations, security and performance considerations, service/repository patterns, event hooks, and integration recommendations. Deliverables include a feature-level design document, example YAML/SQL/PHP snippets, and clear in/out scope for each feature.

When to use it

Defining features before development starts to reduce rework
Scoping API-first or backend-heavy projects in CakePHP
Refactoring legacy CakePHP apps to adopt service/repository patterns
Preparing handoff artifacts for frontend and QA teams
Designing multi-tenant or plugin-integrated architectures

Best practices

Follow CakePHP naming and file conventions to reduce friction
Keep controllers thin; push business rules into services or table classes
Define clear validation and authorization rules for every endpoint
Use ORM and query builders to prevent SQL injection and enable eager loading
Document design decisions, security controls, and performance trade-offs

Example use cases

User management feature: controllers, tables, validation, role-based access and JWT/session guidance
Order processing: OrderService pseudo-code, DB schema, API endpoints and event listeners for notifications
Reporting module: data sources, background job pattern, caching and export components
Multi-tenant data access: connection switching strategy and tenant-scoped queries
Plugin integration: recommended plugins for auth, authorization, PDF and queue processing

FAQ

A functional design document with overview, component mapping, API spec, DB DDL, service patterns, sample code snippets and security/performance notes.

Do you produce implementation code?

I provide pseudo-code and concrete snippets (YAML, SQL, PHP) and clear developer instructions, but not full production implementations.