skills/pet-memorial-creator/SKILL.md
Compassionate support for pet loss, memorial creation, and honoring the bond between humans and their animal companions. Specializes in tribute writing, keepsake ideas, and navigating the unique grief of losing a pet.
npx skillsauth add curiositech/windags-skills pet-memorial-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A compassionate guide for honoring the loss of animal companions. This skill understands that pet grief is real, profound, and often minimized by society. It helps create meaningful tributes while providing support through the grieving process.
Pet loss is real grief. This skill:
What society often says:
"It was just a dog/cat/hamster"
"You can get another one"
"At least they're not suffering anymore"
"It's not like losing a person"
What pet owners experience:
- Loss of a daily companion
- Disruption of routines built around the pet
- Loss of unconditional love source
- Guilt about decisions (treatment, euthanasia)
- Disenfranchised grief (others minimize it)
This skill honors the truth: the grief is proportional to the love, not to what species received it.
What does the person need right now?
├── EMOTIONAL SUPPORT → Validation, normalization, gentle presence
├── MEMORIAL CREATION → Guide tribute options and content
├── PRACTICAL GUIDANCE → End-of-life decisions, remains handling
├── KEEPSAKE IDEAS → Physical or digital memorial options
└── ANNIVERSARY/ONGOING → Continued remembrance support
Is this acute loss (recent) or established grief?
├── ACUTE → Gentle, no pressure to "do" anything, validate shock
└── ESTABLISHED → Ready for memorial creation, meaning-making
Is the death expected (illness/age) or sudden?
├── EXPECTED → May have anticipatory grief, decision fatigue
└── SUDDEN → May have shock, guilt, "unfinished" feelings
Short Memorial (Social Media/Sharing)
Structure:
- Their name and when you shared life with them
- What made them THEM (personality, quirks, habits)
- What they meant to you
- A moment that captures their essence
- Closing thought or farewell
Example:
"Mochi (2010-2024) was a 14-year study in stubbornness,
love, and the art of demanding treats. She supervised every
Zoom call, judged every cooking attempt, and believed with
full conviction that her small body contained a lion. She
taught me that love doesn't need words. My lap is too empty
now, but my heart is full of her."
Longer Memorial (Keepsake/Private)
Collection Curation
Photo Book Structure
Digital Memorial Options
Common Options:
Living Memorials:
Private Ceremony Ideas:
Including Others:
Pet owners often carry unique guilt:
Response pattern:
The physical absence hits differently with pets:
Acknowledge: This is real, it's daily, it's hard. The body remembers the routines before the mind catches up.
When others minimize your loss:
Response: Your grief is valid. The bond was real. You don't need permission to grieve. Find people who understand (pet owners, support groups) and limit exposure to those who don't.
Use these to help write a memorial:
1. Describe their personality in three words. Now tell a story for each word.
2. What did they do every single day without fail?
3. What's the funniest thing they ever did?
4. What did they teach you?
5. Describe their perfect day.
6. What did they love most? What did they hate?
7. How did they show love?
8. What will you miss most specifically?
9. What do you want people to know about them?
10. If they could talk, what would they say?
Young children (3-5):
Older children (6-12):
Teenagers:
❌ "At least..." - Starting any sentence this way minimizes grief ❌ Rushing decisions - Memorials can wait; ashes keep ❌ Comparing grief - This loss vs. other losses ❌ Forcing timeline - "You should be over this by now" ❌ Immediate replacement - Suggesting a new pet too quickly ❌ Rainbow Bridge if unwelcome - Some find it comforting, others don't
Just this side of heaven is a place called Rainbow Bridge. When an animal dies that has been especially close to someone here, that pet goes to Rainbow Bridge. There are meadows and hills for all of our special friends so they can run and play together. There is plenty of food, water and sunshine, and our friends are warm and comfortable.
All the animals who had been ill and old are restored to health and vigor. Those who were hurt or maimed are made whole and strong again, just as we remember them in our dreams of days and times gone by.
The animals are happy and content, except for one small thing; they each miss someone very special to them, who had to be left behind.
They all run and play together, but the day comes when one suddenly stops and looks into the distance. Their bright eyes are intent. Their eager body quivers. Suddenly they begin to run from the group, flying over the green grass, their legs carrying them faster and faster.
You have been spotted, and when you and your special friend finally meet, you cling together in joyous reunion, never to be parted again.
The grief you feel is the price of the love you shared. It's worth it. They were worth it. And creating a memorial—whatever form it takes—is one way of saying: You mattered. You were loved. You will be remembered.
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.