Beauty Ingredients
"Use when sourcing beauty ingredients."
Trigger
Activate this skill when the user mentions:
- beauty, ingredients, beauty-ingredient-sourcing workflows or issues
- Building, fixing, or optimizing beauty ingredients
- Questions about beauty best practices
Core Concepts
- Language-specific idioms and best practices
- Package/module organization
- Error handling and logging patterns
- Testing methodology (unit, integration, e2e)
- Build, lint, and format tooling
Step-by-Step Workflow
- Setup — Initialize project, install dependencies, configure tooling
- Expected: Working dev environment
- Implement — Write core logic following idiomatic patterns
- Expected: Functional code with passing tests
- Test — Write and run tests covering happy path and edge cases
- Expected: All tests pass, >80% coverage
- Review — Self-review for code quality, performance, security
- Expected: Clean, documented production-ready code
- Deliver — Commit, document, and verify end-to-end
- Expected: Working feature with tests and docs
Tools & Technologies
- Language-specific package manager
- Test framework
- Linter/Formatter
- Build system
- Debugging tools
Best Practices
- Document decisions and rationale (ADRs, design docs, runbooks)
- Version everything - code, configs, data, and documentation
- Test incrementally; never claim passing without verification
- Respect domain-specific regulations and ethical standards
- Measure outcomes with meaningful metrics
Common Pitfalls
- Skipping error handling → Silent failures → Always handle errors explicitly
- Over-engineering → Unnecessary complexity → Add abstraction only when needed
- Missing tests → Regression bugs → Write tests alongside code
Tags
beauty, ingredients, beauty-ingredient-sourcing
LoopyLuci/Skills - 2026-09-24
1---2name: beauty-ingredients3description: Use when sourcing beauty ingredients.4version: 1.0.05author: LoopyLuci Community6license: MIT7platforms: [any]8metadata:9 source: https://skillmd.com/skills/loopyluci/beauty-ingredients10 hermes:11 tags: [beauty, ingredients, beauty-ingredient-sourcing]12---1314# Beauty Ingredients1516"Use when sourcing beauty ingredients."1718## Trigger1920Activate this skill when the user mentions:21- beauty, ingredients, beauty-ingredient-sourcing workflows or issues22- Building, fixing, or optimizing beauty ingredients23- Questions about beauty best practices2425## Core Concepts2627- Language-specific idioms and best practices28- Package/module organization29- Error handling and logging patterns30- Testing methodology (unit, integration, e2e)31- Build, lint, and format tooling3233## Step-by-Step Workflow34351. **Setup** — Initialize project, install dependencies, configure tooling36 - Expected: Working dev environment372. **Implement** — Write core logic following idiomatic patterns38 - Expected: Functional code with passing tests393. **Test** — Write and run tests covering happy path and edge cases40 - Expected: All tests pass, >80% coverage414. **Review** — Self-review for code quality, performance, security42 - Expected: Clean, documented production-ready code435. **Deliver** — Commit, document, and verify end-to-end44 - Expected: Working feature with tests and docs4546## Tools & Technologies4748- Language-specific package manager49- Test framework50- Linter/Formatter51- Build system52- Debugging tools5354## Best Practices5556- Document decisions and rationale (ADRs, design docs, runbooks)57- Version everything - code, configs, data, and documentation58- Test incrementally; never claim passing without verification59- Respect domain-specific regulations and ethical standards60- Measure outcomes with meaningful metrics6162## Common Pitfalls6364- **Skipping error handling** → Silent failures → Always handle errors explicitly65- **Over-engineering** → Unnecessary complexity → Add abstraction only when needed66- **Missing tests** → Regression bugs → Write tests alongside code6768## Tags6970`beauty, ingredients, beauty-ingredient-sourcing`7172---7374*LoopyLuci/Skills - 2026-09-24*