---
mdfy_bundle: 1
id: p_mdtSk0
title: "Cross-tool dev workflow"
url: https://mdfy.app/b/p_mdtSk0
document_count: 7
updated: 2026-05-16T14:21:51.031Z
analysis_generated_at: 2026-05-16T14:21:51.031Z
source: "mdfy.app"
---
# Cross-tool dev workflow

> Acme Pulse, a fictional landing-page builder. The seven docs in this bundle are the project's living context — README, auth pattern, DB schema, API conventions, UI patterns, decision log, open questions. Paste this bundle URL into Cursor's .cursor/rules and Claude Code's CLAUDE.md; both AI tools now have the same project memory and stay in sync as the docs update. This is the wedge use case mdfy's URL-as-memory thesis is built around.

## Summary

This collection represents a comprehensive technical documentation suite for Acme Pulse, a landing page builder built on Next.js and Supabase. The documents establish a complete development framework from architectural decisions and UI patterns to database design and API conventions. The project emphasizes vendor consolidation, developer experience, and security-first design through Row Level Security, creating a cohesive full-stack application architecture.

## Themes

- Full-Stack Architecture
- Vendor Consolidation Strategy
- Security-First Design
- Developer Experience Optimization

## Cross-document insights

- The project demonstrates a strategic bias toward integrated solutions over best-of-breed tools, consistently choosing vendors that provide multiple services (Supabase for auth+DB, Vercel for hosting+AI) to reduce operational complexity.
- Row Level Security is positioned as both a security pattern and an architectural decision that eliminates the need for separate authorization services, showing how database-native features can simplify system design.
- The documentation reveals tension between comprehensive patterns (detailed ADRs, strict component hierarchies) and pragmatic shortcuts (open questions, vendor lock-in acceptance), suggesting a mature approach to technical debt management.
- The atomic design implementation creates explicit import restrictions between component layers, which is unusual and suggests the team has experienced problems with circular dependencies or component coupling in previous projects.

## Key takeaways

- Acme Pulse is architected around vendor consolidation and integrated solutions (Supabase, Vercel) to minimize operational complexity while maintaining security through database-native Row Level Security.
- The project establishes comprehensive development patterns from atomic design component hierarchy to ADR-based decision documentation, showing mature engineering practices for a greenfield application.
- Strategic technical debt is explicitly acknowledged and managed through open questions and decision deferral, with clear criteria for when to revisit choices (revenue thresholds, scale limits).

## Open questions / gaps

- Testing strategy and patterns are completely absent - no mention of unit tests, integration tests, or end-to-end testing approaches
- Monitoring, logging, and observability practices are not documented despite mentioning Vercel AI Gateway's observability features
- Deployment and CI/CD pipeline details beyond basic Vercel deployment are missing
- Error handling and debugging patterns for the client-side application are not covered
- Internationalization implementation details are acknowledged as open questions but lack research or spike work

## Notable connections

- **doc:SWys7jXa** ↔ **doc:SrgEHFCI** — The README references the decision log as the source of truth for 'why we chose X' architectural questions
- **doc:SrgEHFCI** ↔ **doc:mjpt9oz8** — The Supabase decision in the ADR is implemented through the detailed RLS authentication patterns
- **doc:wp12y7sM** ↔ **doc:LhYW7tc1** — Form validation patterns in UI connect directly to the API's error handling and validation schemas
- **doc:HsxL91R7** ↔ **doc:mjpt9oz8** — Database schema supports the RLS policies and authentication patterns with organization_members table structure
- **doc:ir0K6-u2** ↔ **doc:SrgEHFCI** — Open questions represent future decisions that will extend the ADR log once research and interviews are completed
- **doc:LhYW7tc1** ↔ **doc:mjpt9oz8** — API authentication methods directly implement the Supabase JWT and token-based auth patterns described in the auth document

## Concepts (this bundle)

- **Tailwind Design Tokens**
- **Atomic Design**
- **ADR Documentation**
- **Row Level Security**
- **Vendor Consolidation**
- **Cursor Pagination**
- **Progressive Enhancement**

## Concept relations

- **Atomic Design** ↔ **Progressive Enhancement** — enables
- **Row Level Security** ↔ **Vendor Consolidation** — supports

1. [Acme Pulse — project README](https://mdfy.app/SWys7jXa)

2. [Auth pattern — Supabase Auth + RLS](https://mdfy.app/mjpt9oz8)

3. [DB schema notes](https://mdfy.app/HsxL91R7)

4. [API conventions](https://mdfy.app/LhYW7tc1)

5. [UI patterns](https://mdfy.app/wp12y7sM)

6. [Decision log](https://mdfy.app/SrgEHFCI)

7. [Open questions](https://mdfy.app/ir0K6-u2)


_Digest view — follow any link above to fetch that doc's full markdown. Add `?full=1` to this URL for the concatenated payload._