haircare-ingredients-analyzer is a library I made, there might be issues with it
this app uses a flat rounded design style so no shadows or sharp edges, also no opacity, just use solid colors from the daisy ui palette
Loading actions...
Skill content
Main instructions and any bundled files for this skill.
haircare-ingredients-analyzer is a library I made, there might be issues with it
this app uses a flat rounded design style so no shadows or sharp edges, also no opacity, just use solid colors from the daisy ui palette
use lucide icons
don't add noreferrer noopener to links
tests go in the tests/src library
tests should mainly be smoke tests, we're just trying to make sure nothing is broken. Don't focus on specific text in tests.
use types from the haircare-ingredient-analyzer library when working with it
get ingredient data directly from haircare-ingredients-analyzer using getBundledDatabase() - do not create separate data files for ingredients
the docs for the haircare-ingredients-analyzer library are in docs/haircareanalyzer.md
the analysis results statuses correspond to the following daisy ui colors:
- caution, warning
- warning, error
- ok, info
DO NOT ADD FEATURES I DID NOT EXPLICITLY ASK FOR
We're using Next 15 NOT 13
don't use rel="noopener noreferrer" on internal links
We are using DaisyUI 5
for mdx components they should have a .not-prose class unless they are really part of the text
Related Skills
Frontend Typescript Linting.mdc
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...
2. Apply Deepthink Protocol (reason about dependencies
risks