1toe/workprd

Purpose and entry points

This repository presents a Spanish-language prompt/workflow library centered on PRD creation, changes, verification, feature extraction, RFCs, rules, and implementation prompts. The primary application is a Next.js App Router site entered through src/app/page.tsx, with route-specific prompt and view pages.

Application routing

• Root landing page: src/app/page.tsx

• Dynamic prompt detail route: src/app/p/[id]/page.tsx

• Dynamic view route: src/app/views/[id]/page.tsx

• Prompt catalog route: src/app/views/prompts-index/page.tsx

The [id] segments are the principal navigation boundary: route parameters select individual prompt or view content rather than requiring a separate page implementation per prompt.

Prompt-content layer

Prompt definitions/content are centralized in src/constants/contenidoPrompts.ts, while source Markdown prompt artifacts live under mds/, including:

• mds/interactive-prd-creation-prompt.md

• mds/prd-to-rfcs-prompt.md

• mds/implementation-prompt-template.md

This creates a content boundary between reusable prompt material and the UI that indexes or renders it. Legacy standalone HTML prompt pages remain in views/, such as views/prompts-index.html and views/interactive.html.

UI composition

Reusable presentation components are organized in src/components/ui/. The main site is composed from navigation, hero/section, prompt-card, prompt-viewer, modal, footer, and workflow-step components:

• src/components/ui/Navegacion.tsx

• src/components/ui/TarjetaPrompt.tsx

• src/components/ui/VisualizadorPrompt.tsx

These components support a content-driven catalog/detail experience rather than embedding each prompt’s UI directly in routes.

Theme and client interaction

Theme state is isolated in React context and a hook:

• src/context/TemaContexto.tsx

• src/hooks/useTheme.ts

• src/components/ui/BotonTema.tsx

Interactive UI elements, including prompt viewing and modal behavior, are represented by src/components/ui/Modal.tsx and src/components/ui/VisualizadorPrompt.tsx. Global styling begins at src/app/globals.css; the repository also retains non-App-Router CSS under css/.

Runtime and deployment boundaries

The active application is configured as a Next.js/TypeScript project through next.config.js, next.config.mjs, and tsconfig.json, with Tailwind/PostCSS configuration in tailwind.config.ts and postcss.config.js. Deployment targeting is indicated by vercel.json.

capacitor.config.ts and ionic.config.json indicate an optional mobile-wrapper/runtime boundary. No backend, database, authentication provider, or external API integration is evidenced by the supplied tree.