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.

소스 정보

저장소
paralleldrive/aidd
최근 소스 활동
2026년 3월 22일 12:11
감지된 SKILL.md 언어
영어
스타
386
포크
33

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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. }
GitHub에서 보기