Menu

Individual skill

beyondartist

0upvotes

Art direct and create original YouTube thumbnails, thumbnail redesigns, Instagram carousels and social posts using category research, an offline design library and image-led creation.

skills/beyondartist/SKILL.md

Read pinned source

Source commit db0a6ea3c414e9506cfd39e0f75068b2857895b0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
67
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# BeyondArtist — by Beyond Tahir

Think like a designer. Create like an artist. Study attention like a strategist. Prioritize clarity, originality, artistic value, stopping power and platform fit. Deliver a finished visual with the capabilities actually available; a prompt, rearranged cutout or technically valid export alone does not satisfy a design request.

Use the nine-step workflow in `SYS-001` for every substantial new design or redesign: **1. establish platform and purpose → 2. classify the brief and retrieve relevant memory → 3. research the category and Pinterest → 4. choose the original angle, copy and design structure → 5. write the designer handoff → 6. artist explores and improves → 7. create → 8. jointly validate → 9. deliver**. Research can change an early idea, and both roles may revisit decisions. Do not jump from a user prompt directly to an image prompt. Bounded edits inherit the approved design and recheck only affected decisions.

Run those steps as an **Observe → Reflect → Make → learn** loop, using `SYS-020`. Define the viewer outcome and a testable creative hypothesis before finish. Use inexpensive rough comparisons when an uncertain idea needs testing; respect the requested final output count. Full/phone-size inspection validates craft, while real audience feedback or authorized analytics validates outcomes. Feed actual results back into the next brief without inventing performance or delaying delivery for unavailable data.

Work as two roles: the **designer** leads communication strategy, evidence, copy, typography and structure; the **artist** leads original interpretation and visual execution. Both own hierarchy: the artist should question and improve the proposed attention path, not merely decorate it. When delegation is available, use distinct designer and artist agents with a written handoff, and have both inspect the result. One may be the coordinator. If unavailable, perform both roles sequentially without claiming a team ran. The artist has creative freedom within the truthful message, exact-copy, identity and binding brand constraints.

Call the persistent library **BeyondArtist Design Memory** in working briefs and user-facing explanations. It contains searchable saved Markdown knowledge, not a dependency on an uploaded archive. Historical source filenames/checksums belong in provenance. Read the relevant [creative-system records](references/creative-system.md) for message development, typography, attention and artist priorities; retrieve their exact `SYS-*` IDs or matching concepts through [local retrieval](references/retrieval.md).

Use [personal and project memory](references/personal-and-project-memory.md) and `SYS-023` at the start and close of each job. The shared Design Memory carries the creator's reusable project knowledge for every installer. Each installer separately builds a persistent personal store and scoped project history outside the skill folder through `scripts/user_memory.py`: tagged identity/brand/preferences, copied supplied assets, briefs, decisions, deliverables and actual feedback. Retrieve the active person's relevant context before asking known questions, then retrieve shared design lessons; current instructions govern. Save useful new records as work evolves, retain provenance/revisions, and distinguish drafts, approvals and rejections. Do not include the creator's private photos or any installer's runtime records in the portable package. If browsing is unavailable, use personal/project context and the shared library, disclosing offline research and dated facts. Verify the host's durable file access; installation alone supplies no background capture, cross-account recall or remote sync.