Add detailed Claude.md and Cursor/rules

[meagancojocar]

Proposed changes

Unreleased product version (optional)

Related issues (optional)

[pulumi-bot]

Your site preview for commit 22f11ac is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-15137-22f11acc.s3-website.us-west-2.amazonaws.com.

[mikhailshilkov]

Two files seem similar but different in many ways. How are we thinking about keeping them in sync vs. entirely independent?

[mikhailshilkov]

What is pulumi-apply?

[thoward]

In this case, it's a short code for Output.apply. See: https://github.com/pulumi/docs/blob/master/layouts/shortcodes/pulumi-apply.html

What the short code does is select the language-specific casing of the apply function (e.g. Apply vs apply) and links to the SDK documentation for whatever language you've chosen, using the chooser framework under the hood.

It's used in these two docs:

• docs/content/docs/iac/concepts/inputs-outputs/all.md

  Line 19 in ba1649a

  If you need to access and use multiple outputs together, the `all` function acts like an [`apply`](/docs/concepts/inputs-outputs/apply/) across many resources, allowing you to retrieve and use multiple outputs at the same time. The `all` function waits for all output values to become available and then provides them as _plain values_ to the {{< pulumi-apply >}} function.

• docs/content/docs/iac/concepts/inputs-outputs/apply.md

  Line 292 in ba1649a

  Ultimately, if you want to view the properties of a resource, you will need to access them at the individual property level. The rest of this guide will demonstrate how to access and interact with a single property using {{< pulumi-apply >}}.

This is a way to avoid the problem I kept running into, for example, in the "Build a Component" docs, where there are subtle variations on the links/names of functions/classes that require entire prose blocks to be within a chooser (and thus duplicated with minor variations in the Markdown). However, you need to write a custom shortcode like that for every scenario and it's not super obvious what the shortcode does. I didn't do that on the components docs, but the original author of the output/apply docs did do that for apply.

[mikhailshilkov]

Suggested change

	author: joe-duffy
	author: author-id

as below?

[mikhailshilkov]

Oh, that works?! Nice if so.

[jkodroff]

I don't think I have anything useful to add to this PR, so no need to wait on my review. Nothing here looks harmful, but I don't have a ton of subject matter expertise. Deferring to Mikhail.

[thoward]

Much of this file seems duplicative of the style guide, readme, and blogging guides. My understanding is that Claude doesn't need much more directive than "read the style guide" to get this information (e.g. it doesn't have to be duplicated within CLAUDE.md, just mentioned there). The concern I have is drift. If we duplicate (or ~mostly duplicate with some subtle variation) between CLAUDE.md and the style guide, which one is the source of truth? which one do we maintain? seems better to keep all this information contained in the style guide, and just ask Claude to use that. That will work for human readers and for agentic AIs equally.