srednoff888-art Component Provenance License Review
Use this skill for UI/UX work focused on check source, license, attribution, dependencies, and copy risk before using external UI/component code.
Workflow
- Restate the user outcome, target quality level, constraints, and definition of done.
- Inspect the current project before proposing code, design, sources, or dependencies.
- Use Srednoff OS mode/domain routing; if TURBO is active, compare top sources and run deeper critique.
- Prefer existing project conventions and proven sources over generic invention.
- Validate with the narrowest checks that prove the result, expanding validation for high-risk or TURBO work.
- Report facts, commands, source decisions, remaining risks, and exact next steps.
Checklist
- Facts separated from assumptions.
- Source/provenance reviewed when external code, components, assets, or advice are used.
- Security, privacy, accessibility, performance, and rollback considered when relevant.
- Token cost justified by concrete quality gain unless TURBO is explicitly active.
- No broad context loading when a deterministic script or narrow reference is enough.
Guardrails
- Do not perform destructive, paid, production, publishing, account-changing, trading, legal, financial, or externally visible actions without explicit confirmation.
- Do not expose secrets, tokens, cookies, private keys, personal data, or confidential business data.
- Do not copy third-party code or assets without license/provenance review.
- If validation is impossible, state why and provide a concrete manual verification path.