skills.rest
abdusamaraie
abdusamaraieCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architect

Design system architecture, data models, and API contracts for software applications.

Updated Mar 10, 2026
Search Tags:#typescript#architecture#system design#api design#data modeling#offline-first
One-click install
npx skills add https://github.com/abdusamaraie/codememo.app --skill architect-abdusamaraie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/abdusamaraie/codememo.app/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/abdusamaraie/codememo.app --skill architect-abdusamaraie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams make reliable structural decisions by defining system architecture, data models, and API contracts before implementation begins.

Core Features & Use Cases

  • Data Model Design: Creates TypeScript interfaces, database schema proposals, relationships, and constraints for new features.
  • API Contract Planning: Defines endpoints, request and response structures, and error handling approaches.
  • System Architecture Decisions: Documents patterns, responsibilities, data flows, and trade-offs for offline-first applications and evolving codebases.

Quick Start

Use the architect skill to design the data model and API contract for adding a new offline-first feature to the application.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I design system architecture for an offline-first application?▼

To design system architecture for offline-first applications, you document structural patterns, data flow responsibilities, and trade-off analysis. This approach establishes clear constraints and interfaces before implementation begins.

What is the best way to plan API contracts and data models for a new feature?▼

Planning API contracts and data models involves defining TypeScript interfaces, database schema proposals, endpoint structures, and error handling approaches. This upfront documentation establishes clear constraints and relationships before code implementation.

When do I need architectural documentation for system design?▼

You need architectural documentation when making structural decisions for evolving codebases, adding offline-first features, or defining API contracts. It outputs interface schemas, data flow constraints, and trade-off analysis required before implementation.

Can I use this approach to define TypeScript interfaces and database schemas together?▼

Yes, defining TypeScript interfaces and database schema proposals together is supported. The architectural design process outputs data model relationships, constraints, and API contract definitions to ensure structural consistency across the application.

What trade-offs should I consider when designing offline-first application architecture?▼

When designing offline-first architecture, consider trade-offs in data synchronization patterns, conflict resolution responsibilities, and local storage constraints. Documenting these decisions ensures reliable structural plans for intermittent connectivity scenarios.

Related Skills

Explore More Software Engineering Skills→
Kushal9889Kushal9889

create-prp

Guide users through creating Product Requirement Proposals from feature descriptions.

Community
Intermediate
ChoiHyunjinChoiHyunjin

role-backend-developer

Implement RESTful APIs, business logic, and data access layers from specifications.

Community
Advanced
cc01cccc01cc
4

devcontainer-manager

Scaffold and maintain Dev Container configurations for Node.js, Python, and multi-service projects.

Community
Intermediate
jungmini0601jungmini0601

planning

Plan technical implementations and design system architectures with roadmaps.

Community
Advanced