playbooks

home / skills / trahoangdev / codex-test / codex-test

codex-test skill

/SKILL.md

This skill helps you set up, run, and edit the codex-test Next.js project with minimal, scoped changes.

npx playbooks add skill trahoangdev/codex-test --skill codex-test

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
531 B
---
name: codex-test
description: "Use when working on the trahoangdev/codex-test repository, including setup, running the Next.js app, and making common edits."
---

# Codex Test Repo

## Quick start

- Install deps: `npm install`
- Run dev server: `npm run dev`
- Build: `npm run build`
- Lint: `npm run lint`

## Project layout

- App Router entry: `app/`
- Global styles: `app/globals.css`
- Tailwind config: `tailwind.config.ts`

## Conventions

- Keep edits minimal and scoped to the request.
- Prefer `app/` for UI changes.

Overview

This skill helps you work on the trahoangdev/codex-test repository, covering setup, running the Next.js app, and making common edits. It guides dependency installation, dev server usage, build and lint commands, and points to key project files and conventions. Use it to make focused, minimal changes following the repository conventions.

How this skill works

The skill inspects the repository layout and provides actionable steps for common tasks: installing dependencies, starting the development server, building production assets, and running lint checks. It highlights the App Router entry, global styles, and Tailwind config so you can quickly locate UI and style files to edit. It also enforces the convention to keep edits minimal and prefer the app/ directory for UI work.

When to use it

  • Setting up a local development environment for the codex-test project.
  • Starting the Next.js dev server to preview changes quickly.
  • Preparing a production build or running lint checks before a PR.
  • Making simple UI edits or style adjustments in the app/ directory.
  • Onboarding new contributors who need a concise workflow.

Best practices

  • Run npm install before any other command to ensure dependencies are present.
  • Use npm run dev for iterative development and fast feedback.
  • Keep edits minimal and scoped to the specific request or issue.
  • Prefer making UI and route changes inside the app/ directory (App Router).
  • Keep global styling changes focused in app/globals.css and Tailwind config in tailwind.config.ts.

Example use cases

  • Add a new page or route under app/ and style it using app/globals.css and Tailwind utilities.
  • Fix a layout or component bug locally: npm run dev, edit files in app/, verify changes.
  • Prepare a pull request: run npm run lint, make small scoped edits, then npm run build to validate production output.
  • Update Tailwind configuration in tailwind.config.ts to expose new utilities used by components in app/.

FAQ

What commands start the project and check it?

Use npm install to install dependencies, npm run dev to start the dev server, npm run build for a production build, and npm run lint to run linters.

Where should I make UI changes?

Prefer the app/ directory because the project uses the Next.js App Router. Keep changes minimal and focused on the request.