Claude Artifact Iteration Loops: Refine Without Losing Context

1. CONTEXT: "We're working on the [Artifact name] Artifact. Currently it has [list what's working]."

2. CHANGE: "I want to [specific change]. Here's exactly what should change: [details]."

3. PRESERVE: "Everything else should remain EXACTLY as is. Do not modify: [list elements to preserve]."

4. VERIFY: "After making the change, confirm that [specific behavior] still works correctly."

CONTEXT: We're working on the DataTable Artifact. Currently it has: sortable columns,
pagination, and row selection with checkboxes. All three features work correctly.

CHANGE: Add a search/filter bar above the table. The search should filter rows
client-side across all columns. Include a clear button and a result count
("Showing 12 of 45 results").

PRESERVE: Sorting, pagination, and row selection must continue working exactly as is.
The existing column definitions and data structure should not change. The visual design
of the table (colors, spacing, typography) should remain identical.

VERIFY: After adding search, confirm that sorting still works on filtered results,
and that pagination correctly reflects the filtered dataset size.

In the LoginForm Artifact, improve the password field validation:

CHANGE: Replace the current basic validation with real-time strength checking.
Show a strength meter below the field with 4 levels (Weak, Fair, Good, Strong).
The meter should update as the user types.

Requirements for each level:
- Weak: < 8 chars
- Fair: 8+ chars, at least 1 number
- Good: 8+ chars, uppercase + lowercase + number
- Strong: 12+ chars, uppercase + lowercase + number + special char

PRESERVE: Email validation, form submission, error handling, and all styling
MUST remain unchanged. Only the password field behavior should be modified.

BUG REPORT: In the DataTable Artifact, sorting a column while on page 2 resets
to page 1 but doesn't re-sort. Expected: sorting should apply and stay on page 2.

ROOT CAUSE: The sort handler is resetting pagination state before applying the sort.

FIX: Change the sort handler to apply the sort FIRST, then reset pagination only
if the sorted order changed the total page count.

VERIFY: After fixing, test that:
1. Sorting on page 2 keeps you on page 2 if results still span that many pages
2. Sorting that reduces total pages correctly moves to the last available page
3. All other table functionality (search, row selection, column resize) is unaffected

STYLE REFINEMENT: Apply a design polish pass to the DashboardLayout Artifact.

CHANGES (visual only — no functionality changes):
1. Increase card border-radius from 8px to 12px
2. Add subtle box-shadow to cards on hover
3. Change primary button color from #3B82F6 to #2563EB (darker blue)
4. Add 0.5px border to all input fields
5. Increase section heading font weight from semibold to bold

PRESERVE: ALL functionality, state management, data flow, and component structure
must remain identical. This is a CSS-only pass.

Before making changes, first reproduce the current Artifact state by saying:

"Show me the current state of the [Artifact name] Artifact."

Wait for Claude to display it. Then:

"Good. Now, make these specific changes to THAT exact Artifact: [changes]."

"Make the following changes and then show me a summary of what changed.
Do not rewrite the entire Artifact — only the modified sections.

Changes:
1. [Specific change 1]
2. [Specific change 2]

After making changes, list:
- What was ADDED
- What was MODIFIED
- What was REMOVED
- What was PRESERVED (unchanged)"

"Before making changes to the [Artifact name] Artifact, save the current version
by displaying it in full. Label it 'Version N - Before [change description]'.

Then create a new version with the changes applied. Label it 'Version N+1 - After [change description]'.

If the new version has issues, I'll ask you to revert to Version N."