agentleFS
fralapofralapo/awesome-agent-skills/skills/freelance-designer-ops/SKILL.md

freelance-designer-ops

Skill1 starsChanged 7 days agoMITView on GitHub

Operating manual for a freelance designer (presentation, graphic or web): what the job really involves, choosing a niche, scoping and timing client projects, consultations and training formats, client communication rules, handling criticism, delegating; a buildable Notion workspace (projects, clients, notes, CRM pipeline, hour tracker with formulas, invoices, content calendar); time management with Google Calendar + Google Tasks (calendars as labels, 1–4 h blocks with goals, batching, energy mapping, notebook triage); tool stack, workspace setup, content creation and yearly review. Use when the user is a freelancer or solo creative planning their week, setting up Notion or a project/hour tracker, estimating how long a deck or project takes, organising clients and invoices, deciding whether to take on work, structuring a consultation or training, or reflecting on growing a freelance practice, even if they don't say 'freelance'.

The file

Files
SKILL.md

Freelance Designer Ops

Chapters: 4 | Corpus: ~35 theoretical transcripts on freelance design practice and productivity | Generated: 2026-11-05

How to Use This Skill

  • Pick the chapter from the Topic Index and read it before giving detailed advice. The chapters contain buildable blueprints (Notion properties, formulas, views) and step-by-step procedures.
  • Adapt to the user's situation (team or solo, their tools). The Notion system was designed for one person and hasn't been proven for teams (ch02 says so).
  • Italy-specific tax notes (partita IVA, forfettario regime, marca da bollo) are flagged in ch01. Treat them as orientation only, not tax advice, and send the user to an accountant.

Core Frameworks

Two jobs in one week: organising (timelines, quotes, invoices, email, calls) and designing. Plan both explicitly. A typical week puts own projects and content on Monday and client work Tuesday to Thursday.

Your freelance "dimension": shape the job from your strengths, weaknesses, aspirations, context and skills, and allow yourself to reshape it. Niche by specialisation (e.g. presentation design) works, but awareness comes before the sale: educate the market first.

Scope before you quote: a client deck takes ~1 month part-time (learning the subject, researching a style, revisions). Ask scope questions up front, because "small" projects grow. Take one project at a time when deadlines are tight. Email is the official client channel. Set working hours and tell clients what they are.

Service formats: consultations of 1–1.5 h, with slides received in advance and fixed live so the client sees a before/after. Training from 2–4 h up to multi-day programmes (in-person is worth more, so cap travel). Content creation is treated as a project where you are the client.

Person / Professional / Project: criticism targets the work and the role, not you. Do a few things well and pass off-topic jobs to other designers. Delegate admin to an accountant and video editing to an editor, each with a set budget.

Notion workspace: Learn → Schematise → Apply: answer four questions on paper (which databases, which relations, which properties, which views), then build. The minimum system is Projects (the hub) ↔ Clients (1 per project) ↔ Notes (many-to-many). One view per question: Overview, a Status board, a Gantt at Quarter zoom, and a Revenue view filtered to active or done projects. Make the statuses Feedback and To invoice explicit. CRM pipeline: Call → Quote → Awaiting reply → Client → Lost/Past.

Hour tracker: dateBetween(End, Start, "minutes") / 60, because "hours" rounds 30 minutes up to 1. Per project, track hours done, hours remaining and % used (over 100% means an overrun). Add an Energy (Low/High) field to decide whether to accept new work.

Time management: one Google Calendar per area, used as a colour label. Work in 1–4 h blocks (typically 4 h; 3–4 h on one design project). Every block gets a goal in Google Tasks. Batch similar tasks, put high-energy work where you're freshest and calls in the afternoon, and leave buffers between events. A paper notebook catches micro-tasks, cleared at day end, and records what you actually did. Move leftovers to tomorrow without guilt.

Good-enough loop breaker: once you've given 100%, stop iterating. Perfectionism loops cost more than they add.

Tools and workspace: keep organisation tools (email, Notion, Calendar, Drive) separate from design tools. Paper first: wireframes and storyboards. Design in the tool you master, then export to the client's. Take inspiration from websites (Behance, Dribbble, Awwwards, Pinterest boards per project), not other decks. Set up the workspace to remove friction: gear left set up, diffuse light, basic acoustics, sit/stand.

Growth: consistency plus a format strategy grows an audience. Keep a written "why" for whom you create. Rough split: 2 days a week for content, 3 for clients. Yearly review: one wellbeing goal, one revenue goal (beat last year by any amount), one lesson per project. When you hit the goal early, pause and rethink instead of grinding out of fear. Say no to work that clashes with your values.


Chapter Index

#TitleKey frameworks
ch01What a Freelance Designer Actually Doesorganise vs. design, freelance dimension, niche, scoping, service formats, criticism, Italy notes
ch02A Notion Workspace for CreativesLearn → Schematise → Apply, 4 questions, Projects/Clients/Notes, views, CRM, hour tracker formulas, invoices, content calendar
ch03Time Management for Freelance Creativescalendars as labels, block + goal, batching, energy mapping, notebook triage, good-enough loop
ch04Tools, Workspace, Content and Long-Term Growthtool split, paper first, inspiration hygiene, workspace setup, content "why", yearly review

Topic Index

  • Clients, communication, limits → ch01
  • Consultations / training formats → ch01
  • Content creation and social → ch02 (pipeline), ch04
  • CRM / lead pipeline → ch02
  • Criticism, perfectionism → ch01, ch03
  • Delegating (accountant, editor) → ch01
  • Estimating project time → ch01, ch03
  • Hour tracking (formulas) → ch02, ch03
  • Invoices and revenue views → ch02
  • Italy: partita IVA, forfettario → ch01
  • Niche / positioning → ch01, brand-strategy-storytelling ch03
  • Pricing, quoting, negotiating, raising rates → pricing-and-sales-negotiation
  • Notion setup → ch02
  • Planning the week / day → ch03
  • Tool stack, workspace, desk → ch04
  • Yearly review, goals → ch04

Related Skills

  • presentation-design / slide-software-techniques: the craft side of a presentation-design practice.
  • social-algorithm: growing a personal brand and audience.
  • pricing-and-sales-negotiation: how to price and quote projects, run discovery calls, handle discounts and objections, raise rates and decline bad-fit clients. Workshop and sprint scoping, day rates and preparation days: workshop-facilitation ch10 (orientation only).
  • brand-strategy-storytelling: choosing and owning a niche, positioning, personal brand, portfolio and case-study storytelling.
  • marketing-mba: market-level positioning, pricing strategy theory, B2B sales pipeline.

Scope & Limits

Practical operating know-how for solo creatives. It is not legal, tax or accounting advice. Notion formulas use the classic syntax, so check them against the current Notion version.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.