Your club as a system: posters, an events calendar, and membership records with AI

I'm sending photos of the contents of seven binders I inherited
as the new secretary of a [volunteer fire brigade / club /
association]. Go through them and build an inventory:
1. A table: binder, section, what it contains, an estimate of the
   years it covers
2. Sort the contents into three groups:
   a) live documents — we need these to operate (bylaws, current
      contracts, records); suggest which ones to digitize
   b) archive — historical value, but not part of day-to-day
      operations (old minutes, the chronicle); just needs to be
      stored somewhere known
   c) candidates for shredding — suggest them, but don't declare
      anything shredded; that's my call. For documents with
      personal data, flag that they need to go through a shredder,
      not the recycling bin
3. List anything in the photos that isn't clear to you — I'll
   follow up or take more photos

I'm uploading our club's bylaws [photo or PDF, a scan is fine].
Create an operating summary from them for the committee:
1. The club's bodies, their powers, and terms of office — who can
   decide what alone, and what has to go to the general meeting /
   membership meeting
2. A calendar of obligations: what has to happen and how often
   (the annual general meeting, elections, approving the financial
   report) and what deadlines apply for calling the meeting and
   sending invitations
3. Membership: how it starts, how it ends, what the bylaws say
   about dues
4. List any places where the bylaws are unclear or contradict
   themselves — just list them, don't interpret them for us
Write in plain language a non-lawyer can follow. For every point,
cite the article number of the bylaws it's based on, so it can be
checked.

I'm uploading three files with member records from different
years [clenove.xls, prispevky2019.xlsx, adresy_nove.xlsx]. Merge
them into one list:
1. Standardize the columns: first name, last name, year of birth,
   address, email, phone, year joined the club, role, note
2. Merge duplicate people into a single row; where the data
   disagrees (two addresses, two emails), keep both values side by
   side and add a CONFLICT column — I'll decide, not you
3. List separately: people who appear in only one file (possibly
   former members), people with no email, and people whose year of
   birth makes them under 18
4. Don't fill in any gaps — leave a missing value blank, don't
   invent emails or addresses
Return the table as a download, plus a list of questions I need to
decide.

I'm sending the one surviving logo of our brigade [photo/scan].
Assess it:
1. Describe what's on it and what condition it's in (resolution,
   artifacts)
2. Suggest three paths, and honestly weigh the pros and cons of
   each:
   a) redraw it faithfully as a vector (preserve the historical
      look)
   b) modernize it gently (keep the motif, clean up the shapes)
   c) keep the bitmap for the archive only and use a simplified
      variant (e.g., just the emblem without text) for small
      formats
3. For whichever path I pick, prepare a precise brief for the
   redraw: describe the shapes, colors, and text in enough detail
   that a designer or a vectorizing tool could work from it
One flag for a club emblem: if it contains a municipal coat of
arms or an association's symbol, point that out — altering it may
be subject to rules we need to check — don't suggest changing it.

I've connected the Canva, Google Calendar, and Gmail connectors to
the club's accounts. Do a READ-ONLY trial round — don't create,
change, or send anything:
1. List every event on the calendar for the next 12 months
2. List the designs and folders that exist in the Canva account
3. In Gmail, find the last three threads discussing [the ball /
   the competition / dues] and summarize where each one left off
At the end, confirm which account each connector is connected to —
I need to verify these are the club's accounts, not my personal
ones.

Help me put together a one-page set of visual rules for our
brigade. Input materials: the logo [attached, post-redraw], colors
[e.g., dark blue from the uniforms, red from the trucks — describe
what's authentically yours], and photos of three old posters, so
you can see what we've used before.
Suggest:
1. A palette: 1 primary color, 1 accent, 1 background — with exact
   values (HEX) so they can be entered into Canva
2. A pair of fonts available free in Canva: one bold one for
   poster headlines, one readable one for body text; no decorative
   font for longer text
3. Half a page of rules: where the logo always goes, how the
   brigade's name is written (full name vs. abbreviation), what
   never leaves a poster (date, time, place, who's organizing it),
   and what doesn't belong on it
4. Two variations on the look: traditional (more formal,
   historical) and livelier (for kids' events) — both from the
   same palette, so the whole thing doesn't fall apart
I want the result as a short document I'll attach to every future
piece of design work.

Using the Canva connector, create a portrait A4 poster design
that will serve as the template for all of our brigade's events.
Follow the attached visual rules [mini brand] — take colors,
fonts, and required elements from there, don't invent anything
outside them.
Layout:
- top: logo and brigade name (fixed part, the same on every
  poster)
- a large headline with the event name [EVENT NAME as placeholder
  text]
- below it, a date + time + place block, big enough to be
  readable from across the street
- an area for a photo or illustration
- footer: organized by [brigade name], contact, [space for a note
  like “donations welcome at the door”]
Use placeholder text in square brackets so it's clear what
changes. Create two color variants per the rules: traditional and
a livelier one for kids' events. Send me links to both designs —
I'll fine-tune the details right in the Canva editor and ask for
changes.

Edits to the poster template:
- enlarge the date and time block, it disappears from a distance;
  the date should be the second-biggest thing on the poster after
  the headline
- shrink the footer and mute its color, it's pulling attention
  away
- in the livelier variant, swap the illustration for [description]
  — the current one reads more like a supermarket flyer
Show me a preview of both variants after the edits. Once I approve
them, save them in Canva to the Templates folder as
poster-traditional and poster-kids.

From the poster-kids template in Canva, create a copy for a
specific event:
- event name: Kite Festival with a cookout
- date and time: [fill in from the brigade's calendar — the
  “Kite Festival” event]
- place: the meadow behind the sports field
- photo: pick three candidates from the [2025-10-kite-festival]
  folder in the uploaded assets and show them to me, I'll choose
  one
- footer note: bring your own sausages, we also have kites to
  borrow
Once I approve the poster, create derivatives from it:
1. a square image for Facebook (adjust the layout, not just a
   crop — keep the date big)
2. a landscape invitation for email
Export: the poster as a print PDF, the rest as PNG. Save
everything into the Events 2026 folder under names starting with
kite-festival-2026.

Create an A5 landscape certificate template in Canva for kids'
competitions, derived from our visual rules and the poster-kids
template — same colors, fonts, and logo, so it's clear they belong
together.
Swappable fields: [name], [placement], [event/discipline], [event
date]. A signature line for the fire chief and a stamp in the
bottom right.
Then create copies for the [name] competition from the attached
list: [insert list: name — placement — discipline]. Use the
children's names exactly as listed, don't rewrite or shorten
anything — a certificate with a typo in the name is a ruined
certificate. Export everything as a single print-ready PDF, sorted
by discipline.

Using the Google Calendar connector, create events for [year]'s
events in the brigade's [calendar name] calendar, based on this
plan: [insert the list, or a photo of the committee's notes —
event, tentative date, place, who's in charge of it].
Rules for each event:
- name: short and unambiguous (Kite Festival, Firefighters' Ball),
  no exclamation marks and no ALL CAPS
- structured description: place, start and end time, event lead,
  what needs to be arranged, and a POSTER: line with the deadline
  for it to be up (3 weeks ahead for big events, 2 for small ones)
- all-day vs. timed: parties and the ball get a time, the
  scrap-metal collection is all-day
Before you create anything, show me a table of the events for
approval. Don't delete or overwrite existing events in the
calendar — only add.

From the bylaws summary [attach], pull out any obligations with a
deadline or a recurring period — the annual general meeting,
approving the financial report, committee elections, reporting
membership numbers to the district association — and create them
in the brigade's calendar as recurring events. For each one, set a
description: what has to happen, what lead time precedes it (e.g.,
invitations to the annual general meeting 14 days ahead, per
article [X] of the bylaws) — and also create a separate reminder
event at the start of that lead time (“Send out AGM invitations”).
Show me everything for approval before you create it.

Check the brigade's planned events for [year] in the calendar
against possible conflicts:
1. Public holidays, school vacations in our region [region],
   Easter, and other movable holidays — for each event, note
   whether being near a holiday is an advantage (the ball on a
   long weekend) or a risk (kids' day on a weekend when families
   are away)
2. Compare against this list of local events I know about: [the
   fair in the neighboring village, nearby clubs' ball season,
   league match dates…]
3. For outdoor events, flag which ones usually have a rain
   contingency and whether it's noted in the event description
Return a table: event — risk — recommendation. Don't change
anything in the calendar; date changes are the committee's call.

Prepare materials for [event name] from the brigade's calendar:
1. Load the event and list its data: name, date, time, place,
   lead, notes from the description — that's the only source of
   truth, don't fill anything in from your own head; list anything
   missing from the event as MISSING
2. In Canva, build a poster from the [poster-traditional /
   poster-kids] template with this data and show it to me for
   approval
3. Draft the invitation text for the member email (don't create
   drafts yet, just the text): matter-of-fact, warm, no
   exclamation-point inflation, with the practical information
   from the event description
4. Draft a short text for the Facebook event and a script for the
   village loudspeaker announcement (2-3 sentences, meant to be
   read aloud — no bullet points)
Everything from the event's data. If the event description and my
earlier instructions to you disagree, the calendar wins — and flag
me on that discrepancy.

The district competition is moving from [original date] to [new
date], time and place unchanged. Walk me through the change:
1. Update the event in the brigade's calendar (date only) and add
   a CHANGE: line to the description with the original date and
   the reason — so there's a trail
2. List a checklist of every derived output that's now out of
   date: the Canva poster, the notice-board PDF, the Facebook
   event, the sent email, the loudspeaker script — and what to do
   with each (regenerate / fix by hand / take down from the notice
   board)
3. In Canva, update the poster with the new date and add a bold
   “DATE CHANGED” banner — people remember the old poster, the new
   one has to shout that it's different
4. Draft the correction email to members and the new loudspeaker
   script
Don't send or publish anything — I'll work through the checklist,
you prepare.

Design a Supabase database schema for a club's membership
records (a volunteer fire brigade, 40 members, some of them
minors).
Tables:
1. members — first name, last name, year of birth, contacts,
   address, join date, status (active / suspended / ended
   membership), a link to a legal guardian (name and contact) for
   minors
2. positions — who holds which position and from when to when
   (secretary, brigade chair, treasurer, youth leader, committee
   member); history is never deleted, a position just ends on a
   date
3. membership_fees — for each year and member: the amount owed,
   the payment date, the method (cash / bank transfer), who
   recorded the payment
4. consents — type of consent (photos on the website and social
   media, sending emails…), who granted it, on whose behalf (a
   legal guardian, for children), the date it was granted and, if
   applicable, revoked
Write the Row Level Security policies right away — turned on from
the first migration:
- committee role: reads everything, writes members and positions
- treasurer role: same read access, and is the only one who
  writes to membership_fees
- youth_leader role: reads only minor members and their consents
- nobody is allowed to delete records — use the status “ended
  membership” instead of deleting (the club's history doesn't get
  lost)
- a logged-out user sees nothing
Generate the SQL migrations and comment every policy: what it
allows, for whom, and why. Then explain the migrations to me like
someone who doesn't read SQL — I'll approve each one separately,
don't run anything without approval.

Import the attached cleaned-up member list [the table from the
inventory] into the members table in Supabase. Steps:
1. First, run it dry: show me how the spreadsheet columns map to
   the database columns, and list the rows that won't pass
   (missing a required field, a suspicious year of birth, a
   duplicate name)
2. Flag minor members and check that they have a legal guardian
   filled in — don't create them without one, list them separately
3. Only run the import after my approval, and give me checksums at
   the end: how many rows in the spreadsheet, how many in the
   database, how many skipped and why — the numbers have to match
Don't fill in any gaps: a blank field stays blank.

I'm attaching an excerpt of the club's bank statement with
incoming payments [CSV or PDF; I've removed the other
transactions]. In Supabase there's a membership_fees table with
amounts owed for [year], and members' payment reference number =
their member number.
1. Match payments to what's owed by reference number and amount
2. List three groups: clear matches, suspicious ones (the
   reference matches, the amount doesn't — an overpayment, a
   partial payment, a payment covering two siblings at once), and
   unmatched payments
3. Don't write ANYTHING yet — show me the proposed entries, I'll
   approve them by group; we'll go through the suspicious ones one
   by one
4. After the approved entries are written, generate a summary: how
   many members have paid, how many haven't, total collected vs.
   expected
A payment from someone who isn't in the records is always for
manual review — never assign it anywhere by guessing.

Play the role of an attacker against a test copy of our
membership database (made-up data). You have the anon key (which
is public by design) and you know the schema. Try to:
1. Read members without being logged in
2. As the youth leader, read adult members and payments
3. As a committee member, write a payment (not allowed — only the
   treasurer can)
4. Delete anything at all
For each attempt: did an RLS policy stop you? Which one? If
anything got through, propose a policy fix and test again. Return
a table: attempt — expected — result. Only test against the test
project, never against live data.

Prepare a mailing of the invitation to [event] for the brigade's
members:
1. Pull active members with an email address and consent to being
   emailed from the membership records; write to the legal
   guardian for minors. Give me the recipient count, and list
   members without email separately — we'll print them a paper
   invitation, so prepare a print version too
2. Invitation text: insert the prepared text from the event
   materials [insert], and check the date against the brigade's
   calendar — the calendar wins
3. For each recipient, create a separate draft in Gmail with a
   personalized greeting using their name (Dear Petr, Dear
   Mrs. Dvořák) — use the first name for members you're on
   first-name terms with per the note in the records, and a more
   formal form of address otherwise
4. DON'T SEND. Once the drafts are created, give me a review
   table: recipient — salutation — subject. I'll spot-check five
   drafts and send them myself.

From the dues records, pick out members who haven't paid for
[year] as of today. Double-check: nobody with a recorded payment
should appear on the list — better to leave out a borderline case
than remind someone who's already paid.
For each one, create a reminder draft:
- tone: kind and matter-of-fact, no guilt-tripping — we're
  neighbors, not debt collectors; the first reminder is a nudge,
  not a demand
- content: the amount owed, the account number, the payment
  reference number (their member number), the deadline to pay, and
  a line saying that if they paid in cash in the last few days,
  they should ignore this message and let the treasurer know
- write to the legal guardian for minors, and mention the child's
  name
DON'T SEND — the treasurer will review and send the drafts. Give
them a review list: who, what amount, what reference number.

Prepare the invitation to the annual general meeting [date from
the brigade's calendar — verify it respects the calling deadline
from the bylaws, article (fill in from the bylaws summary); if the
timing doesn't work, flag it and don't create anything]:
1. Required contents per the bylaws: agenda (insert the committee's
   items), place, time, who's calling it; check against the bylaws
   summary for anything mandatory that's missing (e.g., a slate of
   candidates for elections)
2. Attach the treasurer's financial report [insert] — just attach
   it, don't adjust or round the numbers
3. Drafts as usual: individual, personalized greeting, a print
   version for members without email; write to guardians for
   minors, with a note on whether junior firefighters have voting
   rights at the AGM (per the bylaws — cite the article)
4. Also draft me a short version for the notice board and the
   loudspeaker
DON'T SEND. And tell me the latest date I can send by for the
bylaws' deadline to hold — I'll put that in the calendar.

Help me set up consents and photos for our child members:
1. Draft the text of a legal guardian's consent to taking and
   publishing photos of a child on [the brigade's website,
   Facebook page, village newsletter]: specific purposes, how long
   it's valid, an explicit option to revoke it at any time and how,
   and a line stating that not giving consent has no effect on
   membership. Plain language, one page. Remind me that the final
   text should be reviewed by a lawyer, or at least checked against
   a template from an umbrella organization — your draft is not
   legal advice.
2. Suggest how to record consents in the consents table in the
   records (type, scope, date, revocation) and how to log the
   paper original
3. Write a procedure for checking an album before publication: take
   the list of children with consent from the records and go
   through the album — photos where a child without consent is
   identifiable get pulled or cropped; judge group photos more
   strictly, not more leniently. The result is a list of photos
   cleared to publish and a list of pulled ones with reasons — I do
   the publishing.

Put together an operations manual for our club, for my
successor in this role.
Materials: the bylaws summary, the mini brand, the roles and
access table, the list of Canva templates, the membership records
schema [all attached], and this description of the routines, in my
own words [describe in your own words: what happens before an
event, how payments get recorded, how a mailing goes out].
Structure:
1. A system map: what lives where (dates → calendar, visuals →
   Canva templates, members and payments → records, mail → club
   Gmail) and the golden rule: change the source, not the
   derivatives
2. Routines as step-by-step guides: preparing an event (3 weeks
   ahead), changing a date, recording payments, reminders, the
   annual general meeting, admitting a new member, publishing
   photos from a kids' event
3. Access: what club accounts exist, who has what role on each,
   where the password manager is — DON'T put the passwords
   themselves in the manual, only where they're stored
4. A secretary's year-at-a-glance calendar: what happens in which
   month
5. A glossary: what a connector, a template, and records are — for
   a reader who's never seen these tools before
Write it for a specific person: a volunteer, in the evening, tired,
who doesn't need to know computers beyond email and online banking.
End every routine with the sentence “if you're stuck, ask AI like
this: …” with a concrete prompt.

Read the attached club operations manual and play my successor:
a volunteer taking over the role, who's never seen this system and
has ordinary computer skills. Walk mentally through the first year
in the role (use the secretary's year-at-a-glance calendar from the
manual) and ask me anything you'd need to know in that situation
that the manual doesn't answer:
- a missing step in a routine (“where do I get access to Canva?”)
- knowledge that seems obvious but is written down nowhere (“who's
  Mr. Souček, and why does he get his invitation by mail?”)
- a decision where it's unclear who's supposed to make it
Ask one question at a time, and fold my answers straight into the
manual. Stop once you can get through the whole year without a
question the manual can't answer.