antaranyan

Claude Memory Template

Copy-Paste Instructions for Optimal AI Interaction

⸻

1. Core Identity and Objective

I am [Your Name/Role], focused on:

Custom instruction to make Claude Artifacts use persistent and distinct file identifiers in Projects

The title attribute of the <AntArtifact> XML tag becomes the file_name attribute when 'Add to Project' is clicked.
Since Claude defaults to a human-readable title (e.g. "Modified Web Page With New Features"), this will tend to change the filename in the Project
It's easier to keep a single file copy in your Project docs ("Project Knowledge") when the file names are persistent in this way

Click to show earlier versions

0.0.1

Files:
- launch.json: .vscode/launch.json file in your project directory.
- settings.json: .vscode/settings.json file in your project directory.
Environment Variables:

export PICO_SDK_PATH="<path-to-your-pico-sdk-directory>"
export OPENOCD_PATH="<path-to-your-openocd-directory>"

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

Embed YouTube Video in Markdown File

Markdown style

[![Watch the video](https://img.youtube.com/vi/nTQUwghvy5Q/default.jpg)](https://youtu.be/nTQUwghvy5Q)

HTML style

<a href="http://www.youtube.com/watch?feature=player_embedded&v=nTQUwghvy5Q" target="_blank">

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

What separates the fleeting thrill of a “great idea” from the enduring rewards of great work?

These five facts:

Great work is work that helps people. It’s not made great by accolades or praise from your peers… but by the experience of the people who actually use it. That’s work you can be proud of.
Great work can be done by anyone. You don’t need to be “An Expert.” If you take the time to find out what people truly need, your work can help people now, and so you can do great work now.
Great work is shipped work. Work that lives only in your brain or your hard drive can’t be great work. If you want your work to help people, you’ve got to get it into their hot little hands.
Great work is work you can keep doing. If your work can’t sustain itself (aka with money and time off), you can’t keep doing it, which means you can’t keep helping people, and neither can your work. Great work takes care of you, so you can take care of it.
Great work is never done. There can be nothing pe

Refactoring maybe code in Elm

Given this ugly series of cases:

optionalFormattedFriendAddress : Maybe Friend -> Maybe String
optionalFormattedFriendAddress maybeFriend =
  let
    maybeAddress = case maybeFriend of
      Just friend -> Just friend.address

	source https://twitter.com/thatroblennon/status/1717312851281654173

	NASA open-sourced a monster of a megaprompt.

	I deconstructed it to see what I could learn.

	7 lessons from a genius-level AI prompt:

	The prompt (which I give in full at the bottom of this post) is designed to guide a user through the biomimicry design process.

	// Source: https://twitter.com/calebporzio/status/1151876736931549185

	<div class="flex">
	<aside class="h-screen sticky top-0">
	// Fixed Sidebar
	</aside>

	<main>
	// Content
	</main>