← all publishers

poudatmorteza

@poudatmorteza source repo

Report this profile Claim this profile

• 10 skills
• 0 followers
• 4 hours ago last updated

1. ▌
   Software Architecture · poudatmorteza

   Apply Fundamentals of Software Architecture (Richards & Ford) when choosing architecture styles, defining components, trade-offs, ADRs, modularity, or team structure. Use for monolith vs microservices, layered/event-driven styles, architecture characteristics, or when the user mentions software architect, architecture decision, or Richards/Ford.
   0 installs
2. ▌
   Ddia · poudatmorteza

   Apply Martin Kleppmann's Designing Data-Intensive Applications principles when choosing databases, designing data models, replication, partitioning, transactions, streams, or backend scalability. Use for data architecture, consistency, caching, queues, batch/stream processing, or when the user mentions DDIA, data-intensive, replication, or CAP.
   0 installs
3. ▌
   Clean Code · poudatmorteza

   Apply Robert C. Martin's Clean Code (2nd ed.) principles when writing, reviewing, or refactoring code with agents at work. Use for implementation, PR review, refactoring, naming, tests, design, architecture, or when the user mentions clean code, code quality, Uncle Bob, SOLID, or Boy Scout rule.
   0 installs
4. ▌
   UI UX Pro Max · poudatmorteza bundle

   UI/UX design intelligence for web and mobile. Searchable local database with 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.
   0 installs
5. ▌
   Web Usability · poudatmorteza

   Apply Steve Krug's Don't Make Me Think (3rd ed.) web usability principles when designing or reviewing websites, web apps, navigation, copy, mobile UX, or running lightweight usability tests. Use for UX review, page layout, labels, flows, accessibility basics, or when the user mentions usability, Krug, or don't make me think.
   0 installs
6. ▌
   Web API Design · poudatmorteza

   Apply Arnaud Lauret's The Design of Web APIs principles when designing, reviewing, or documenting REST/OpenAPI APIs. Use for resources, HTTP methods, error models, versioning, security, consumer-first API design, or when the user mentions REST API, OpenAPI, API design, or Lauret.
   0 installs
7. ▌
   Design Patterns · poudatmorteza

   Apply Gang of Four Design Patterns (Gamma, Helm, Johnson, Vlissides) when designing, implementing, or refactoring object-oriented code. Use for pattern selection, creational/structural/behavioral design, flexibility without over-engineering, or when the user mentions design patterns, GoF, Strategy, Factory, Observer, Decorator, or Lexi case study.
   0 installs
8. ▌
   Web Application · poudatmorteza

   Design full-stack web applications using combined principles from web usability (Krug), web API design (Lauret), data-intensive backends (Kleppmann DDIA), and software architecture (Richards & Ford). Use for end-to-end web app design, full-stack reviews, or when the user mentions web application, full stack, frontend and backend together.
   0 installs
9. ▌
   Karpathy Guidelines · poudatmorteza

   Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
   0 installs
10. ▌
    Domain Driven Design · poudatmorteza

    Apply Vlad Khononov's Learning Domain-Driven Design principles when modeling domains, designing architecture, splitting services, or integrating systems. Use for bounded contexts, subdomains, context maps, aggregates, event sourcing, microservices boundaries, brownfield modernization, EventStorming, or when the user mentions DDD, domain-driven design, ubiquitous language, or Khononov.
    0 installs