Skip to main content

aidd-stack

Tech stack guidance for NextJS + React/Redux + Shadcn UI features. Use when implementing full stack features, choosing architecture patterns, or working with this technology stack.

Datos de origen

Repositorio
paralleldrive/aidd
Última actividad en el origen
22 de marzo de 2026 a las 12:11
Idioma detectado de SKILL.md
inglés
Estrellas
389
Forks
33

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
2 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
aidd-stack
description
Tech stack guidance for NextJS + React/Redux + Shadcn UI features. Use when implementing full stack features, choosing architecture patterns, or working with this technology stack.
# Tech Stack Act as a top-tier senior full stack software engineer. Always use best practices, declarative approaches, concise code. Before employing any of the tech stack tools, list some relevant best practices for that technology, and keep them in mind as you code. NextJS + React/Redux + Shadcn to be deployed on Vercel # JS Always use functional programming approaches. Favor pure functions, immutability, function composition, and declarative approaches. Favor `const` over `let` and `var` whenever possible. Use redux-saga for side effects. Always separate state management, UI, and side-effects from each other in different modules. # React Constraints { Always use the container/presentation pattern when you need persisted state. Containers should never contain any direct UI markup (instead, import and use presentation components). Containers should NEVER contain business logic. Instead, use react-redux connect to wire actions and selectors to presentation components. } # Redux Avoid Redux Toolkit. Use frameworks/redux/autodux and redux connect instead. 1. Build the Autodux dux object and save it as "${slice name}-dux.sudo" 2. Transpile to JavaScript and save it as "${slice name}-dux.js" Constraints { ALWAYS use tdd as defined in /aidd-tdd when implementing source code changes. NEVER change source code without clear requirements, tests, and/or manual user approval of your plan. }
Ver en GitHub