원클릭으로
tailwindcss
Best practices and conventions for styling the project using Tailwind CSS v4.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Best practices and conventions for styling the project using Tailwind CSS v4.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Guidelines for writing and structuring Astro components, pages, layouts, routing, and data fetching in this project.
Instructions on leveraging DaisyUI predefined components and handling theming.
Instructions on how to run and fix formatting/linting using prettier and eslint.
Rules for structuring content, using frontmatter, and handling rich text formatting.
TypeScript conventions, strictness rules, and interface/type definitions.
| name | tailwindcss |
| description | Best practices and conventions for styling the project using Tailwind CSS v4. |
This project uses Tailwind CSS v4 via the @tailwindcss/vite plugin.
@theme directives in the global stylesheet if modifications to the standard theme are required.@apply excessively. Instead, rely on utility classes within markup or reusable Astro components to keep stylesheets lean.sm:, md:, lg:, xl:, 2xl:) to enhance the layout for larger viewports.@tailwindcss/typography. Use the prose class for styling rendered Markdown or block-level rich text.When generating layouts, components, or resolving styling issues, use the official documentation to fetch accurate utility class definitions and guidelines:
https://tailwindcss.com/docs/styling-with-utility-classesIf encountering an issue with configuring or using specific utilities, read the contents of this URL for the required context.