Cursor Pro RSS: brief a coding agent for feed work

Give the task repository context

Identify the source records, feed generator, public output, and validation command. Describe how the project assigns identifiers and canonical URLs. A task such as adding full article content should say where that content comes from, how summaries remain available, and which output file a reviewer should inspect.

Cursor's rules documentation describes project rules stored in the repository and scoped to the codebase. Use project guidance for durable conventions: preserve existing identifiers, keep publication dates stable, use the project's XML serializer, and include feed changes in the documented validation process. Keep temporary debugging observations in the task itself.

Provide fixtures that expose the problem

A useful feed fixture contains the edge case you are trying to handle. For an escaping bug, include punctuation and a code sample. For a migration bug, include an old item whose title and canonical path have changed while its identifier remains constant. Keep the fixture small enough that a maintainer can read it directly.

Task: preserve the item ID when its slug changes.
Inspect: article records and RSS serialization.
Verify: edited item keeps its ID and uses its new canonical link.
Deliver: a focused change and the validation result.

Ask for an explanation of the source of the error before broad edits when the behavior is unclear. A wrong date can originate in content metadata, timezone conversion, or serialization. Changing all three layers at once makes it harder to assess which change actually solved the problem.

Review the public result

• Compare the relevant source record before and after the change.
• Parse the generated XML with the project's validator.
• Check the edited entry's identifier, link, date, and content.
• Confirm that unaffected entries remain consistent.
• Inspect the code diff for unrelated changes or new dependencies.

Keep the accepted task and its fixture with the project where they remain useful. The goal is to improve the publishing system's behavior, not to accumulate lengthy agent instructions that restate every line of code. Use the IDE workflow guide to organize the surrounding development routine and make future feed changes easier to review.