-
Create new Automator application with Run Shell script action (exact steps below).
- Open Automator.app (e.g. from Spotlight)
- Select File → New in menu
- Select "Application", click "Choose"
- With "Actions" toggle selected, type "Run Shell Script" in filter box, double click on filtered item
-
Put contents from
lock_spotify_version.shinto script's body (exact steps below). -
In opened right-hand item select
/bin/shas "Shell" type and copy contents of Gist's "lock_spotify_version.sh" below/in text area
Discover gists
| #!/bin/ash | |
| # ======================================================== | |
| # Setup a Dumb AP for OpenWRT | |
| # Tested on: Belkin RT3200 (aka. Linksys E8450) 22.03.3 | |
| # Script expects factory settings | |
| # Copy the script file to your /tmp folder with SCP | |
| # SSH your router | |
| # Type sh /tmp/dumb_ap.sh | |
| # ======================================================== | |
| # Disable IPv6 |
| """ | |
| Patch the creation of database migrations in Django | |
| Import this early from `__init__.py``. | |
| - Don't want verbose_name changes in the migrations file. | |
| - Don't want help_text in the migrations file. | |
| """ | |
| from functools import wraps | |
| from django.db.models import Field |
| --- | |
| name: frontend-design | |
| description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. | |
| license: Complete terms in LICENSE.txt | |
| --- | |
| This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. | |
| The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. |
People
:bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
| #!/usr/bin/env bash | |
| # checck if pidof exists | |
| PIDOF="$(which pidof)" | |
| # and if not - install it | |
| (test "${PIDOF}" && test -f "${PIDOF}") || brew install pidof | |
| # find app in default paths | |
| CO_PWD=~/Applications/CrossOver.app/Contents/MacOS | |
| test -d "${CO_PWD}" || CO_PWD=/Applications/CrossOver.app/Contents/MacOS |
| According to all known laws of aviation, there is no way a bee should be able to fly. | |
| Its wings are too small to get its fat little body off the ground. | |
| The bee, of course, flies anyway because bees don't care what humans think is impossible. | |
| Yellow, black. Yellow, black. Yellow, black. Yellow, black. | |
| Ooh, black and yellow! | |
| Let's shake it up a little. | |
| Barry! Breakfast is ready! | |
| Coming! | |
| Hang on a second. | |
| Hello? |
Original solution can be found here: http://answers.unity.com/answers/477764/view.html
This is an editor script to reverse an AnimationClip. Since it's an editor script you have to put it in a folder called "Editor". Once it's there a new mainmenu item called "Tools" will appear (if not just click the "File" menu once).
Now you have to duplicate the AnimationClip in Unity by pressing CTRL+D while you have selected the AnimationClip. Select the duplicated Clip and click on Tools/ReverseAnimation. This will reverse the animation.
This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.
Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.
How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.