skills.rest
phishkatlabs
phishkatlabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

solutions-architect

Turn research into system designs, database schemas, API contracts, and frontend structure.

Updated Aug 27, 2026
Search Tags:#architecture#documentation#monolith#system-design#db-schema#api-contracts
One-click install
npx skills add https://github.com/phishkatlabs/phishkat-crew --skill solutions-architect-phishkatlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solutions-architect
Source: https://github.com/phishkatlabs/phishkat-crew/tree/main/solutions-architect
Command: npx skills add https://github.com/phishkatlabs/phishkat-crew --skill solutions-architect-phishkatlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges research to technical implementation by turning research into concrete system designs, schemas, contracts, and frontend structure that engineers can implement.

Core Features & Use Cases

  • Designs comprehensive system architecture, including boundaries, data flows, and external integrations.
  • Generates database schema and API contracts with detailed field types, constraints, and ownership for multi-tenant readiness.
  • Produces a frontend component structure and routing plan to guide UI implementation from design.

Quick Start

Create a complete system-design document covering architecture, database schema, API contracts, and frontend structure for a SaaS product.

Frequently Asked Questions about solutions-architect

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

FAQPage Schema
How do I turn product research into a system design document?▼

To turn product research into a system design document, you translate complete, unambiguous specifications into architecture, database schema, API contracts, and frontend structure. This bridges research to technical implementation by producing production-ready outputs for cross-team alignment.

What is needed to generate API contracts and database schema for a SaaS application?▼

Generating API contracts and database schema requires complete, unambiguous specifications for endpoints, data models, ownership, and non-functional requirements. This ensures the resulting schemas include detailed field types, constraints, and multi-tenant readiness.

Can I design frontend structure and routing plans from system architecture?▼

Yes, designing frontend structure and routing plans from system architecture is possible. The process produces a frontend component structure and routing plan that directly guides UI implementation from your design specifications.

What is the best way to document system boundaries and data flows?▼

The best way to document system boundaries and data flows is to generate a comprehensive system architecture design. This approach explicitly maps boundaries, data flows, and external integrations to enable cross-team alignment before implementation begins.

Does system design generation work without detailed non-functional requirements?▼

No, system design generation does not work without detailed non-functional requirements. It requires complete, unambiguous specifications for endpoints, data models, ownership, and non-functional requirements before producing production-ready architecture and contracts.

Related Skills

Explore More Software Engineering Skills→
schpetschpet
5

speccer

Convert unstructured notes into a structured docs/spec.md specification document.

Community
Intermediate
ChurchCRMChurchCRM
933

churchcrm

Plan and implement ChurchCRM development using Slim 4, Perpl ORM, and Bootstrap 5/Tabler patterns.

Official
Advanced
adnanmuelleradnanmueller
2

senior-frontend-engineer

Translate design specs and API contracts into Next.js frontend interfaces.

Community
Advanced
nicholasgriffintnnicholasgriffintn
2

backend-design

Plan backend systems, APIs, and data models with structured architecture decisions.

Community
Basic